AEM Sites Playbook, Chapter 15: SEO, metadata and the URL lifecycle
Do public URLs, metadata and locale relationships express the intended page?
November 10, 2026
Make metadata an owned output
Use this chapter when launching, renaming or migrating pages, or when search/social previews show the wrong information. Inventory page title, description, canonical URL, locale alternates, robots directives, sitemap inclusion, structured data and social metadata. Assign where each value originates: author-entered property, template/component, frontend, mapping or delivery configuration.
Check delivered output as well as stored properties. The canonical-URL discussion begins with a field not appearing in page code. The author rejects the first cache explanation; a later mapping suggestion has no confirmed outcome. That case justifies tracing property-to-output behavior rather than prescribing a cache flush.
Use Adobe's page-property reference and SEO/URL guidance for the applicable deployment. Validate the intended public domain/protocol and the consistency of titles, canonical output, sitemap URLs and navigation. Record whether a value is present in the initial response or added later by the frontend. Do not assume a custom component or headless consumer emits the same metadata as an AEM-rendered page.
Manage URL changes as content changes
For a moved, renamed or replaced page, identify old entry points, intended destination, redirect behavior, internal links and the owner of the rule. Test representative exact requests through the real domain, including relevant query/locale variants. Check chains, loops, missing targets and unintended matches of API or asset paths.
Cloud Service offers pipeline-free URL redirects with documented configuration boundaries. In the RewriteMap discussion, the author reported success after changing both a map name and TTL. The final follow-up challenged the naming explanation. Do not claim underscores are prohibited or that a particular TTL is a universal repair; inspect map generation, content, virtual host and rule application separately.
Record approval for a redirect-map update as deliberately as approval for the content it changes. A marketing-maintained map still needs validation and rollback ownership. The servlet rewrite case also belongs in the regression set: a page URL rule can intercept a non-page request.
Keep locale relationships consistent
Maintain an owned mapping of equivalent locale URLs and verify it alongside translated content. The EDS/Universal Editor hreflang question supplies a concrete architecture but no confirmed implementation. Its accepted generic statement that only one method may be used is too strong.
Google's primary guidance treats HTML, HTTP-header and sitemap methods as equivalent and permits them together, with no additional Search benefit from multiple implementations. Choose an approach the team can maintain and verify consistent alternate/return relationships. Do not invent an EDS-specific server-rendering or edge-rewriter recipe from that discussion.
Follow each value from editorial input to public output
Community discussions highlight separate checks for stored values, generated markup and delivered routes. The canonical-URL example has no confirmed repair; the redirect example changes more than one variable before reporting success; the hreflang example leaves its delivery-specific implementation open. Keep those uncertainties visible in the acceptance record.
Scroll horizontally if needed.
| Element | Ownership decision | Practical verification |
|---|---|---|
| Title and description | Which fields/templates supply the value and brand suffix? | Inspect delivered output for missing, repeated or overridden values |
| Canonical URL | Which public URL represents the page? | Check domain, protocol, path and unintended duplicate tags |
| Locale alternatives | Who owns equivalent-page relationships? | Verify actual corresponding pages and consistent alternate/return relationships |
| Sitemap | Which URLs should it represent? | Compare intended published URLs, absolute form and reachable output |
| Redirect | Who approves the old/new relationship? | Test actual status, destination, chains, loops and unintended matches |
| Social preview | Which title, description and image should sharing services receive? | Inspect implemented metadata and an approved preview process |
| Private/test content | How is access enforced? | Actual denied access independently of crawl directives |
Use page properties and URL guidance for the AEM branch in use. A headless or Edge Delivery frontend must have an explicit metadata contract; the property existing in Author does not prove that consumer emits it.
Worked scenario of a localized product rename
The URLs and results below are hypothetical. A company renames a product on English and French pages while retaining an older entry URL used in customer material. The new pages need correct metadata, a corresponding locale relationship, an approved image and a deliberate old-URL redirect.
The content owner supplies the intended title, description, image and equivalent locale pages. The SEO/delivery owners agree the public URLs and where markup is generated. The redirect-map owner prepares the approved relationship, using the supported mechanism for that environment.
Scroll horizontally if needed.
| Request or output | Expected result |
|---|---|
| Old English product URL | Intended redirect to the approved replacement, without a loop/chain |
| New English page | Correct public canonical and one intended title/suffix |
| New French page | Correct local metadata and the intended equivalent relationship |
| Sitemap | Intended new URLs with the correct public domain/protocol |
| Social metadata | Approved image/title/description for the destination page |
| Unrelated API endpoint | Existing method/path behavior is unaffected by page rewrites |
The team retrieves actual output rather than approve a screenshot of page properties. It compares the markup/headers and the real redirected response. Locale owners inspect the linked content, not just the language code.
Suppose the English result is correct but the French canonical still names the previous domain. The old English redirect works, while an unrelated POST endpoint gains an unwanted suffix. The page rename remains on hold: two independent delivery defects would otherwise be hidden by the successful primary redirect.
After correcting the scoped rules and metadata generation, the same request set passes. The owner approves the defined rename and locale scope, retains rollback instructions for the map/configuration change and schedules observation after publication. No ranking improvement is inferred from the passed checks.
Maintain locale mapping once and verify its consumers
Choose an authoritative place for equivalent-page relationships and identify the implementation owners who consume it. This might support sitemap, markup and navigation behavior, but the actual design must be tested for the chosen delivery model.
Google's primary guidance permits equivalent hreflang methods together, without additional Search benefit from multiple implementations. That does not make inconsistent outputs acceptable. Verify actual targets, reciprocal relationships and the chosen maintenance approach rather than copy the accepted generic EDS reply as an implementation solution.
Operate metadata and redirects after launch
Scroll horizontally if needed.
| Trigger | Required review |
|---|---|
| Page move/rename | Old/new URL mapping, internal links, canonical, sitemap and sharing output |
| Domain change | Protocol/domain generation, redirects, certificates/routing and external consumers |
| Locale addition | Corresponding content, alternates, navigation and local metadata |
| Shared template/component change | Duplicate/missing tags and affected existing pages |
| Withdrawal | Intended response, replacement/redirect, sitemap and remaining references |
Keep redirect ownership and review dates with content lifecycle records. Validate new rules against relevant non-page paths and unchanged pages. A managed redirect map still needs authorization, test evidence and an operator who can reverse an incorrect change.
Verify discovery and sharing
Check that published, intended pages are reachable and represented correctly in the relevant sitemap and page output. Confirm private/test content is protected through actual access controls; robots directives are not an authorization mechanism. Review the social title, description and image through the platform's approved preview process when preparing publication. Social markup remains an implementation responsibility, not a proven default for every AEM project.
Complete W15 with metadata ownership, old/new URL mapping, locale relationships, response evidence and validation results. Include withdrawn pages and domain changes. Business owners accept the intended presentation; practitioners verify the delivered markup and route. Track discovery outcomes after launch without promising rankings from metadata or sitemap changes alone.
W15 Metadata and URL lifecycle
Use with chapter 15. Inspect the actual public response.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Public URL, title/description/canonical and origin of each value | [enter] |
| Domain/protocol, locale alternates and corresponding URL map | [enter] |
| Robots/sitemap/structured-data/social metadata requirements | [enter] |
| Old/new URL, redirect approval and expected status/destination | [enter] |
| Initial/delivered markup, actual response and loop/chain tests | [enter] |
| Withdrawal/private-content behavior and metadata owner | [enter] |
