When Should You Update Brand Context Files After a Redesign?

Your redesign shipped, but your AI drafts still link to URLs that now redirect and pitch a positioning you retired months ago. That gap between the new site and the old context is where tone drift and robotic AI mush come from. The fix is to update brand context files after redesign work is finished, at a specific moment instead of whenever someone notices.

Your redesign checklist almost certainly covered redirects, canonicals, and sitemaps. It almost certainly skipped the context your AI reads before it writes, so those files still describe a site that no longer exists.

This guide gives you a trigger-based answer. It includes an impact matrix that maps five redesign changes to the files they affect, a rule for when to recrawl and when to edit by hand, a six-step sequence, and a stale-context check. One change type gets past every recrawl, and it is the one teams miss most often.

Before you start, you need three things: the redesign live, your redirect map in hand, and access to your editable Markdown context files.

Short answer: Update your brand context files once the redesigned URLs are live and every redirect is verified, and before you generate the next 30-day content calendar. If you update earlier, you lock in URLs that may still change. If you update later, a full month of drafts inherits stale links and outdated positioning.

Which Redesign Changes Mean You Should Update Brand Context Files?

Update brand context files when a redesign changes your URLs, pillar pages, navigation templates, or positioning. Purely visual changes need no update.

Brand context files are the eight editable Markdown files the AI reads before it drafts any article. They are generated from your domain's sitemap and published pages. They hold the voice rules, keywords, internal links, and SEO guidelines your site had at crawl time.

Here is how that works in practice. At setup, you enter a domain. BloGoose finds its XML sitemap, inspects the published pages, and generates the files. A redesign then changes the sitemap those files were built from, and every row in the matrix below is a version of that mismatch.

Visual-only: leave the files alone

New colors and fonts don't change what the AI writes about, so refreshing the files adds risk and no value. This row is best for designers who want to ship without touching the content pipeline.

Navigation and templates: check seo-guidelines.md

Template changes can alter breadcrumbs and schema output. This row is best for technical SEO leads who own the markup.

Restructured URLs: refresh internal-links-map.md

A new URL structure retires the paths your drafts currently link to. This row is best for growth leads who manage site architecture.

New pillar pages: update target-keywords.md and the calendar

A recrawl finds the new pages. You still need to decide which keywords each pillar owns. This row is best for content leads who plan topic clusters.

Repositioning: edit brand-voice.md, competitor-analysis.md, and features.md

This is the change type a recrawl can't catch. It is best for founders who own the message.

Why a recrawl misses repositioning: A crawl reads what you published, not what you decided. When a redesign changes URLs, templates, or pillar pages, those changes exist in the sitemap and on live pages, so a recrawl picks them up. Repositioning is different. A new audience, a dropped competitor, or a reframed feature set often lives in strategy documents before it appears in page copy. Even after the copy changes, a crawl can't tell which claims are now core and which are leftovers. The rule is simple: structure changes call for a recrawl, and strategy changes call for manual edits to the voice, competitor, and features files.

Standard redesign checklists handle redirects and canonicals well. They just don't extend to the files an AI writer reads.

How to Update Brand Context Files After a Redesign, Step by Step

Update the files in six steps: launch, verify redirects, update the sitemap, recrawl, hand-edit strategy files, then regenerate the calendar. Each step depends on the one before it, so the order matters more than the speed.

Prerequisites: the redesign is live, you have your redirect map, you can submit sitemaps in Google Search Console, and you can open your editable Markdown context files.

1. Launch the redesign. Push the new templates and URLs to production. When this step is done, the new pages load publicly. Don't touch the context files before launch, because staging URLs and draft copy will leak into new articles.
2. Verify every 301 redirect. Test each old URL on your redirect map. Expect this to take 30 to 60 minutes for a mid-sized site. When this step is done, each old URL returns a single 301 hop to its new path. Don't recrawl before this step, or the crawl will record broken paths.
3. Update and resubmit the XML sitemap. Confirm that the sitemap lists only the new URLs, then resubmit it in Search Console. When this step is done, Search Console shows the sitemap with a recent read date.
4. Recrawl or re-extract site context. Run the crawl again so the structure-driven files refresh. When this step is done, internal-links-map.md and seo-guidelines.md reference only the new URLs and templates.
5. Hand-edit the strategy files. Open brand-voice.md, competitor-analysis.md, and features.md, and rewrite the lines that describe old positioning. Plan on about 30 minutes. When this step is done, no retired claims remain.
6. Regenerate the 30-day calendar, then ask Google to crawl new posts. Never regenerate the calendar before step 5 is finished. When this step is done, the planned topics reflect your new pillars.

Here is a worked example for restructured URLs. Suppose /blog/guides/ became /resources/. Verify the redirects first, then refresh internal-links-map.md before any new draft is generated.

Why internal-links-map.md must refresh after redirects and before drafting: The AI chooses internal links from internal-links-map.md, not from your live site. If the map still lists retired paths, every new draft links to URLs that now redirect. Each of those links adds a redirect hop for readers and crawlers, and none of them points straight to the canonical page. If you refresh the map before the redirects are verified, it may record paths that later change or break. If you refresh it after drafting starts, you have to fix the links post by post. Refreshing it between those two moments means every draft links straight to the live, final URL.

Because the files are editable Markdown, you change only the affected lines. You don't rebuild your context from scratch, and the voice rules you've already refined stay intact.

Once the files are updated, confirm they actually reflect the new site.

How to Check Your Context Files Are Current

Generate one test draft after the update and scan it for five stale-context symptoms. Each symptom points to the one file that needs fixing.

1. Internal links point to retired or redirected URLs. Links that hit a 301 or 404 mean internal-links-map.md still lists the old structure. Recrawl the site so the map pulls live URLs from the new sitemap.
2. Intros repeat old positioning or taglines. A draft that opens with last year's pitch means no one edited brand-voice.md. Rewrite the positioning lines by hand, because a crawl cannot infer strategy.
3. Calendar topics target retired pillars. Topics about products or categories you dropped show that target-keywords.md is outdated. Replace the retired pillars, then regenerate the calendar.
4. Comparisons name old competitors. Drafts that benchmark against rivals you no longer position against point to a stale competitor-analysis.md. Update the competitor list to match your new market.
5. Schema or breadcrumb guidance no longer matches the templates. Instructions that describe the old page templates come from seo-guidelines.md. Align them with the redesigned markup before you publish.

Run the same check on older posts during a content refresh so live articles stop linking to dead pages.

Brand Context Files After a Redesign FAQ

These answers cover timing and strategy questions the steps above leave open.

How soon after a redesign launch should I recrawl my site?

Recrawl once redirects resolve and the new XML sitemap is live, not in the launch hour. A crawl that runs too early captures half-migrated URLs, so internal-links-map.md inherits broken paths. First confirm that redirects return clean 301s and that the sitemap lists only new URLs.

Do stale context files affect AEO citations?

Yes. Outdated positioning and links to dead URLs weaken the passages that answer engines extract and quote. Current context files keep claims consistent across every draft. That consistency supports AEO optimization because AI systems see one accurate version of what you do.

Do I need to regenerate the whole calendar after repositioning?

Yes, but edit first. Manually rewrite the positioning lines in brand-voice.md, then regenerate the calendar so new topics reflect the new position. If you regenerate before the edit, you get topics built on your old pitch and retired angles.

Can a recrawl update my brand voice automatically?

No. A recrawl refreshes structural data like URLs, sitemaps, and templates, but voice and positioning are strategic choices. Hand-edit brand-voice.md to lock in the rules every draft follows.

Re-Run Setup on Your Redesigned Domain

Update brand context files whenever a redesign touches structure or strategy, and do it in the right order. Match the change type to its file, recrawl for structure, hand-edit for strategy, and regenerate the calendar last.

The order matters because each step feeds the next. A calendar built before you edit positioning locks old thinking into 30 days of drafts.

Your next step is to re-run setup in BloGoose on the redesigned domain. Then review the fresh 30-day calendar and confirm that the first drafts link to live URLs and carry your new positioning. When an AI SEO content engine reads current context, every article it ships matches the site you just built.