Beam is hiring a US Storytelling and Marketing Lead, an Australian marketing lead, a Product Marketing Manager and a Content Creator, all of whom will publish pages meant to rank. But every beam.org page we checked tells search engines its real address is on next.beam.org (the homepage's canonical is "https://next.beam.org/en-us"), and next.beam.org redirects straight back. Search engines get a loop instead of a clear address, and the US, UK and Australian versions have no hreflang tags to tell them apart.
First action
Change the canonical base URL setting in Webflow and re-publish.
How to measure it
Organic sessions
- Now
- –
- Target
- +30%
- By
- 2 quarters
Steps
Fix the base URL
Webflow SEO settings: canonical base https://beam.org.
Webflow site owner 1 hour
Re-publish and check
View source on ten pages; each canonical should be its own beam.org URL.
Webflow site owner 1 hour
Add hreflang
en-us, en-au, en-gb and x-default for every page with versions.
Webflow site owner 2 days
Root files
robots.txt and sitemap.xml reachable from every country.
Webflow site owner 1 day
Search Console
Submit the sitemap; inspect key URLs.
Webflow site owner 1 day
Retire next.beam.org
Keep the 301s, remove it from any settings.
Webflow site owner 1 hour
Monitor
Indexed pages and organic sessions by country.
Senior Product Analyst monthly
Why it works
In Webflow, set the site's canonical base URL to https://beam.org so each page canonicalizes to itself, then add hreflang tags linking the en-us, en-au and UK versions of each page (plus x-default). Check that robots.txt and sitemap.xml are reachable at the root for every country (from the US they currently redirect to /en-us/ paths that return 404) and submit the sitemap in Search Console.
Clear canonicals and language tags are the base for every page the new team writes: customer stories, sector pages and thought leadership only rank if search engines know which URL and which country version to show.
Ready to use
ChecklistSearch basics for beam.org
[ ] Canonical base URL = https://beam.org [ ] Each page canonical = its own URL [ ] hreflang en-us / en-au / en-gb / x-default [ ] /robots.txt reachable (200) from US, UK, AU [ ] /sitemap.xml reachable and submitted [ ] Page titles and meta descriptions on every page [ ] next.beam.org 301s kept, not referenced
Risks and how to handle them
Locale redirects confuse crawlers
Serve each locale at a stable URL and use hreflang rather than redirects alone.
Evidence
- Your websiteEvery page we fetched on beam.org (October 22, 2026, re-checked later the same day) sets its canonical tag to a next.beam.org address, for example the homepage to "https://next.beam.org/en-us" and the Notes page to "https://next.beam.org/en-us/product/notes"; next.beam.org answers each with a 301 back to the beam.org page. No page carries hreflang tags for the US, UK and Australian versions. From a US connection, beam.org/robots.txt and beam.org/sitemap.xml redirect to /en-us/robots.txt and /en-us/sitemap.xml, which return 404.Source
- HiringStorytelling and Marketing Lead (USA, posted October 22, 2026) to "build brand awareness and drive pipeline across the US": "Customer stories via our website, video, blog, one-pagers and social", "PR, partner and influencer marketing", "Sales and BDR enablement", "Demand generation via paid and organic channels", "Long form thought leadership including ebooks and research reports", and "Building influencer networks with membership bodies and trade press"; "the sole marketer for your vertical". A matching Communications and Marketing Lead is being hired in Melbourne for Australia (posted October 2, 2026), including "Events and field marketing including conferences and customer dinners".Source
- HiringProduct Marketing Manager (London, posted October 16, 2026), the "Founding Product Marketing Manager": owns "end-user communications, lifecycle activation and product marketing collateral"; "Running lifecycle campaigns in Customer.io to drive product adoption, with a particular focus on activating users of our Notes product - this is the largest part of the role"; "writing help centre articles, in-app updates, and release notes"; a "fortnightly product newsletter".Source
- HiringContent Creator (London, posted October 13, 2026): "own our social media presence", "primarily focused on creating a strong employer brand", plus "community-focused content around Beam's mission"; "Support senior leadership's personal content/LinkedIn presence"; source stories "sensitively ... especially where social workers and their clients are concerned". Every Beam job post links "an armful of awards" to beam.org/awards. Beam also hires frontline caseworkers (Caseworker - Employment Specialist, Southwark).Source