Ballad
Surface

Sitemap and site audit

Ballad maps your whole site daily and reads it against your positioning and what Google needs: ten checks, each finding carrying the fix: write it, refresh it, copy it for your agent, or close it.

~5 min7 sectionsYour whole site

Most of your website was written before Ballad arrived, and it's the part buyers read first. In Content, the rail's Website group holds Sitemap, where Ballad keeps a map of it, and Audit, which tells you what to write, refresh or fix.

It's a marketing audit first: it reads your pages against what you now say you do. It also checks the technical side, so you hear when Google can't reach, index or load a page.

The sitemap

Ballad crawls your site daily and keeps every page it can find as a tree: your product and pricing pages, your docs, and everything it has published itself.

That map does more work than it looks:

  • Articles link to your real pages (the actual pricing and docs URLs) instead of inventing plausible ones.
  • Posts and pages have somewhere to point when they need a next step.
  • The audit has something to read.

Page collections expand in the tree rather than folding into one row, since each landing page is a destination of its own.

The ten checks

The audit runs over that map and your positioning, plus your Search Console data and the AI answer monitor where they're relevant:

CheckWhat it looks for
TechnicalWhat stops Google reaching, indexing or loading a page: robots.txt, noindex, broken links, speed
CoveragePages the positioning promises and the site doesn't have
Message driftPages still saying what the positioning no longer says
SearchPages slipping, within reach, or competing with each other
LeaksReaders with no next step, and next steps nobody reaches
AI answersPages an answer engine can't quote
LinksOrphans, dead ends, and articles that never send readers on
MetadataTitles, descriptions, social images and canonicals
FreshnessYears and phrases that have gone stale
Dead weightPages nobody visits, finds or links to

Drift is treated as serious only where being wrong costs you something: a price, an offer, a claim about your beta. A vague product page is not drift.

Coverage also uses keyword data: when people search for alternatives to a competitor you track and no page of yours compares the two, that's a finding, with how often it's searched.

The technical check

  • robots.txt rules that block Googlebot from the site, a key page, a page in your sitemap or an article.
  • noindex on a key page or a sitemap page, from a meta tag or the X-Robots-Tag header.
  • Broken internal links: links to pages known to be gone, plus a rotating sample of new link targets checked each week.
  • Google's URL Inspection, from Search Console, for your key pages and recent articles, with advice for whatever state Google reports.
  • Page speed on mobile for your home page, your sign-up page and your newest article: real-user Core Web Vitals when Chrome has them, otherwise the lab score, with the biggest fixes Lighthouse names.
  • Structured data that doesn't parse.

If your site's firewall turns Ballad's reader away while it answers people, that's one high finding here too: what answered, why it matters (the page list goes stale and the audit can't read your pages), and the setting to change, ready to copy. Ballad never poses as a browser.

A check that couldn't run, because of a quota or no Search Console, leaves its open findings open rather than marking them fixed.

A finding, and its fix

Each finding says what's wrong, which page, and how bad it is, and carries the fix rather than leaving you to do it:

  • Write it: a coverage gap becomes a brief, or a landing page of the right type.
  • Refresh it: a slipping article is rewritten in place, at the same URL.
  • Copy: the detail, for a page Ballad doesn't own.
  • Copy for Agent: the finding as a task (the page, the issue, the exact change, how to tell it's done), to paste into Claude Code or a ticket.
  • Fixed / Dismiss: closes it. A dismissed finding doesn't come back in the same words.

The same concern on many pages is one card listing the pages: its Copy for Agent carries every instance in one task, and Fixed or Dismiss closes the lot. One by one opens the pages that need their own fix.

Anything high-severity also appears in your Inbox, so the things worth acting on reach you without opening this page.

When it runs

Weekly, and never on a stale map: the crawl refreshes first, then the audit reads it. Run the audit does the same on demand.

Model reads are sticky: a page that hasn't changed since it was last read isn't read again, so a weekly audit on a stable site costs almost nothing and a page you rewrite gets looked at afresh.

Linking your articles to your site

A common first finding on a young site is that nothing you've published ever links to your product. Ballad can fix that in a pass across your back catalogue: it proposes the links first, and applies them only when you say so, republishing each article at the same URL.

Next

Next guideCampaigns