Content, URLs & SEO
This page covers three things that matter to anyone thinking about search and site structure: how your page addresses (URLs) are built, how content that's generated externally lands in your site, and which fields visitors and search engines can actually see versus what stays internal.
How page URLs and structure are built
Every page has a slug — the short, human-readable part of its address (for example, best-bonuses). A page's full URL is built from its slug plus its place in the site's hierarchy, so a page nested under a parent inherits that parent in its path.
Because the URL is assembled from these parts, two things follow:
- Slugs matter for SEO. They're visible in the address, so keep them short, descriptive, and stable.
- Changing a slug or moving a page changes its URL. That can break existing links and lose search ranking unless the change is intentional and handled.
Changing a published page's slug changes its live URL. Treat slug changes on established pages as deliberate decisions — anyone linking to the old address, including search engines, will land on the old path until it's updated or redirected.
Where externally-generated content comes in
Some content isn't written by hand in the editor — it's produced externally (for example, by an automated content pipeline) and sent into your site, where it arrives as a normal, editable page. Once it's in, it behaves like any other content: you can review it, edit it, and arrange its blocks.
Two things to keep in mind:
- It usually arrives as a draft. That gives you a chance to review before it goes live.
- After it lands, it's yours to edit. Changes you make in the editor are ordinary content edits — the external source doesn't keep overwriting them.
What visitors and search engines can actually see
Not everything stored on a page or operator is public. Origin deliberately separates two kinds of information:
- Public — the content meant for visitors: page copy, titles, operator details shown on the page, and SEO fields like the page title and meta description.
- Internal — data used to run the system but never meant for visitors: affiliate and redirect links, editorial notes, sync identifiers, and internal flags. These are locked down so they don't leak into the public site or its data feeds.
For SEO and product decisions, the safe assumption is: don't treat an internal field as if it were public. If you need a piece of information to be visible to visitors or search engines, confirm it's a public field rather than an internal one.
The fields that shape how a page appears in search — its title and meta description — are content you control directly on the page. Filling them in thoughtfully is one of the highest-impact things you can do; leaving them blank means search engines guess on your behalf.
Frequently Asked Questions
- Can I change a page's URL?
Yes, by changing its slug or moving it in the hierarchy — but on a published page that changes the live URL, so plan for redirects and updated links.
- Will editing an externally-generated page get overwritten later?
No. Once the content is in your site, your edits are normal content changes; the external source doesn't keep re-writing the page.
- Is an internal field like an affiliate link visible to visitors or search engines?
No — internal fields are locked down and don't appear on the public site or in its public data. If you need something to be visible, use a public field.
- What's the single best SEO habit here?
Set a clear, unique page title and meta description on every page, and keep slugs short and stable.