Hand over the reason as well as the rule
When switching AI coding agents, preserve why each intentional SEO exception exists. A file list and a request to keep SEO intact leave too much to interpretation. The next assistant needs to understand which URLs serve different audiences and which decisions depend on the current publishing workflow.
Matt Hollingshead's 3 November website checklist raises the risk of AI edits changing intentional SEO settings. Google's canonical documentation supplies the technical context. My proposed handoff turns those decisions into a short record that survives the original chat.
Inventory exceptions rather than every tag
Start with decisions that a new assistant might reasonably misinterpret: a campaign page pointing to a main service page, an old URL redirected after a rename, or a filtered archive view excluded from independent indexing. Record the affected path, intended behaviour, business reason and responsible owner.
Keep the record close to the project instructions and link to the implementation. Avoid pasting a large frozen copy of every meta tag. That becomes another source of drift. Record the stable intent and the evidence needed to check it against the site as it exists today.
Give the next agent a bounded change brief
A fictional consultancy asks for a new layout on a campaign landing page. Its brief can state that the page supports paid traffic, shares substantial content with a service page, and retains the existing canonical preference pending an explicit editorial decision. Layout changes and URL strategy then have distinct owners.
Ask the assistant to identify affected routes and any SEO rule it believes needs changing before implementation. This is a project working rule, not a claim that every canonical decision needs bureaucracy. Routine edits can proceed while exceptions remain visible and unexplained changes are caught early.
Check the delivered page after the edit
Compare the response status, canonical, indexing directives and relevant navigation before and after the change. Where JavaScript is involved, inspect the initial response and rendered page. Google explains crawling, rendering and indexing as separate stages; a browser screenshot alone cannot establish the delivered metadata.
Check a few neighbouring routes that use the same template. A shared component may affect more than the page named in the request. Retain a concise before-and-after record and investigate differences against the intended rule, rather than treating every change as either harmless or automatically wrong.
Update the decision record when intent changes
A canonical preference is not a guarantee that Google will select that URL. It also should not be preserved forever when the content strategy changes. If a campaign becomes a distinct permanent offer, revisit the decision, document the new purpose and remove obsolete instructions.
For teams using reusable AI skills, this record can become part of a website editing workflow. JQ's web design service can prepare the initial decision inventory and acceptance checks. The useful deliverable is a maintainable handoff that explains what the next editor must preserve and why.
Link Map
Sources and editorial review
Assigned to the 3–9 November 2026 editorial series. This edition was prepared and source-checked on 9 November 2026; assigned dates do not imply prior public deployment. Proposed workflows and illustrative examples are JQ AI SYSTEMS editorial analysis, not completed client experiments.
- Matt Hollingshead, Search Engine Land: 7 technical SEO checks for vibe-coded websites (3 November 2026; practitioner analysis and editorial trigger).
- Google Search Central: Specify a canonical URL (publication date not shown; checked 9 November 2026; standing primary technical documentation).
- Google Search Central: JavaScript SEO basics (publication date not shown; checked 9 November 2026; standing primary technical documentation).