By Greg Nowak. Updated 6 November 2026.
If your website has accumulated AI-assisted articles, the difficult question is which pages deserve more of your team’s time. Some may help customers choose a service. Others may repeat the same advice across dozens of URLs, with nobody responsible for checking the details.
Start with a practical test: does this page help a customer understand something, make a decision or complete a task—and can your business stand behind its answer? Use that test to build a manageable queue of pages to keep, improve, merge or remove.
What Google’s AI content guidance means for your audit
Google’s guidance on generative AI content recognises useful applications such as research and structuring original material. It also calls for manual factual review before publication, including titles, descriptions, structured data and image alternative text.
Its scaled content abuse policy targets generating many pages primarily to manipulate rankings while offering little value, regardless of how they were created. Where content meets that definition, Google says to exclude it from Search. Assign that work explicitly rather than leaving it in an open-ended editing queue.
The decisions below are an editorial workflow. They are not a Google scoring system.
Give every page a job before judging its performance
Create an inventory with one row per published URL. Record its audience, purpose, owner, last review date and related pages. Add available search traffic, enquiries, useful incoming links and any known use by sales or support.
Complete this sentence for each page: “This page helps this audience make this decision.” A service name or keyword is not enough. For example, “website migration” is a topic; “help an operations lead understand migration responsibilities before requesting a quote” gives the editor something concrete to deliver.
Start with consequential claims, prominent commercial pages and repeated templates. Low traffic can justify investigation, but it should not decide removal on its own. A page may resolve an objection that sales teams encounter regularly.
Check the claims a customer could act on
Review statements about prices, compatibility, availability, limitations and promised outcomes. For each consequential claim, record the wording, supporting evidence and reviewer. Prefer current product documentation or confirmation from the person responsible for delivering the service.
Evidence must support the actual promise. “Available with an additional module” does not justify “included as standard.” If support is missing, assign someone to verify, narrow or remove the claim.
Sampling can reveal problems across a large collection, but it cannot approve a whole page. If a sampled claim fails, widen the review to related pages using the same template. Complete the factual review before approving the revision.
Choose an action someone can finish
Give each URL a decision, a reason and an owner. Use specific acceptance criteria so an editor or agency can complete the work without guessing.
| Decision | Choose it when | Required next step |
|---|---|---|
| Keep | The page serves a distinct need and its claims are verified. | Record approval, ownership and the next review trigger. |
| Improve | The purpose is useful, but the answer is incomplete, inaccurate or hard to use. | Specify missing evidence, practical detail and metadata fixes. |
| Merge | Several pages answer substantially the same question. | Select a surviving URL, preserve useful material and map redirects. |
| Remove | No useful purpose or material remains after review. | Check dependencies, approve withdrawal and define the old URL’s response. |
“Add more detail” is a weak brief. “Explain which integrations are supported, identify exclusions and replace the unsupported setup-time promise” is work someone can deliver and another person can check.
Merge overlapping answers—and handle the old URLs
Read related pages side by side. What would a customer lose if you combined them? Different introductions and keyword variations offer little reason to maintain separate pages. Different audiences, constraints or buying decisions may justify them, provided those differences appear in the answer.
Choose the surviving URL using relevance, existing links and business use. Preserve verified material, then update internal links and the sitemap to reflect the final structure.
For a permanent merge into a relevant replacement, use a server-side 301 or 308 redirect, following Google’s redirect guidance. If a removed page has no suitable replacement, return 404 or 410; Google’s HTTP status documentation explains that these responses lead to removal from its index over time. Avoid sending every retired article to the homepage.
Make approval part of the CMS workflow
Store supporting sources, the reviewer, review date, unresolved issues and approval status alongside the content. Agree which changes require another review: a changed service specification or an edited commercial promise should have a clear owner.
Include metadata in approval. Check that the title and description promise what the page delivers, structured claims match visible information, and alternative text describes the image appropriately.
WordPress revisions can compare and restore saved versions, but retention can be limited or disabled. Check your installation and test restoration before a large editing batch. Verify whether custom source fields and SEO metadata are retained too; keep the decision record separately where necessary.
Check the published result before closing the task
Compare the live page with the approved version. Test redirects, retired URLs, internal links and the enquiry route. Record a baseline for relevant search traffic and enquiries, then review results over an appropriate period. Separate completed editorial work from later search outcomes.
If your team needs help turning the audit into delivered changes, Greg can help scope the review, coordinate editors and developers, and define acceptance criteria. Bring a URL export, the main concerns and the people responsible for approval. Talk to Greg about managing the content cleanup.
Related on GrN.dk
- JavaScript-Heavy Service Pages Still Lose Leads: What to Audit in 2026
- Google’s AI Search Toggle Is a Publishing Decision, Not an SEO Setting
- Google’s AI Search toggle needs a test plan, not a gut decision
Need help with this kind of work?
Talk to Greg about your content cleanup Get in touch with Greg.