Running a content audit

Refresh your inventory, review coverage, save content decisions, and export the filtered results.

1. Refresh the inventory

Open Analytics → Content Audit. Expand Configure the crawl. Choose Analytics, Apps, or both. Add your website URL if you also want a crawl. Then choose Build. The header's Refresh inventory button uses those same choices.

Analytics reads page data from Google Analytics and Search Console. Apps reads published social posts from supported accounts. A crawl checks website text and page details. An API call or import may add other sources. The screen does not select all sources by default.

The build saves its progress as it runs. You can leave the screen and come back later. A failed crawl shows an error. Retry build resumes a saved crawl where possible. A build with no usable sources shows a failure.

Expand Build source notes to see skipped sources and crawl warnings.

2. Review coverage

Use Count and Traffic to compare page counts with search clicks. A dash means unknown traffic. Click a cell to see its pages. Gaps refer to the pillars and stages you chose in brand setup. Check that plan before you write new content to fill a gap.

Tag my content fills missing pillar, audience, and stage tags. Score brand fit checks website text against your brand's rules. Both run in the background. You can retry pages that could not be read. Review the results before you act on them.

3. Work through the library

Choose All, Site, or Social. Use Table or Grid to view the same rows. Search or filter to focus your review. Clear filters brings back the full list.

Change a row's tags, action, or audit status. Select rows to change them as a group. Selection applies to the current page. It clears when you change pages or filters. If some saves fail, those rows stay selected so you can retry them.

A failed inline save shows a message and restores that field. Other successful edits stay saved. An action is a plan. It does not publish or delete content, set up a redirect, or create a Studio draft. Do that work in your publishing tool.

4. Export a working artifact

Open Export and choose Google Sheet, CSV, or Sitemap XML. An export uses the active filters across all matching pages. It does not use just the visible page or the checked rows. A sitemap includes eligible website URLs only.

Sheets needs a Google Drive connection. After the export, use the link to open the new sheet. You can keep the link and return to it later.

An export can hold up to 20,000 matching rows. Narrow the filters if it is too large. The library shows up to 3,000 matches from a scan of 10,000 saved rows. Coverage and summary counts use up to 10,000 rows. Capped views show a notice. Source limits may further affect which pages a build finds.

Who can do what

Viewers can review, filter, and export. Editors and admins can also start a build, run analysis, and change audit decisions.

Last updated 2026-09-15