Pre-Publish Checks
Check new pages before they create another duplicate-content problem.
A pre-publish checker helps teams catch overlapping intent, weak answer structure, missing schema, and thin AI-search signals before a draft goes live.
The cheapest duplicate-content fix is preventing the extra page before it goes live.
A draft can look useful in isolation while still competing with a page that already exists. That is why pre-publish review should check the draft against the site library, not only against a keyword list.
Before publishing, confirm the target intent, scan for nearby pages, strengthen answer sections, add the right schema, and make sure internal links point to the right owner.
Content Miner is built to make that review repeatable: check the page, compare it to the content map, and decide whether the draft deserves a new URL or belongs inside an existing asset.
How to audit this page type
A useful content audit should be repeatable. Instead of rewriting from instinct, build a small evidence trail for the URL, the pages around it, and the reason a change is worth making.
1. Check the page by itself.
Start with the public checker so the page has a baseline across SEO, GEO, AEO, and AIO. For pre-publish checks, the first pass should show whether the page has enough visible structure, metadata, headings, and answer coverage to deserve deeper review.
2. Compare it against the surrounding content.
A single URL can look fine until it is compared with the rest of the site. The site scan is where duplicate intent, repeated answers, weak ownership, and competing internal links become easier to see.
3. Choose the smallest honest action.
The right fix is not always a rewrite. Some URLs need a stronger summary, some need schema cleanup, some should be merged into a better page, and some should stay because they serve a distinct role.
What to check before changing the page
- Confirm the page has one clear job and that the title, H1, summary, and primary section headings all support that job.
- Compare the URL against nearby pages before rewriting. Pre-Publish Checks issues are often library issues, not isolated page issues.
- Check whether the page is indexable, canonical to itself, included where appropriate in the sitemap, and reachable from internal links.
- Look for answer-ready sections: a direct explanation, useful examples, limitations, and a next step that fits the reader's intent.
- Record the decision before making changes so the team knows whether the URL should be combined, differentiated, updated, or kept.
This keeps the audit grounded. The goal is not to create more pages or chase a score in isolation. The goal is to make the strongest page easier to find, easier to understand, and easier to trust.
Practical audit notes
Prevent the overlap before launch.
A draft can be useful and still create a duplicate-content problem. Pre-publish review should compare the draft against the existing library before the new URL becomes another cleanup task.
Decide whether the idea needs a new URL.
Some drafts should become sections inside an existing page. Others deserve a new URL because they target a different intent, audience, product, or decision stage. The checker should make that decision easier before publishing.
FAQ
How does Content Miner evaluate pre-publish checks?
Content Miner looks at the page in context: the visible content, metadata, headings, schema signals, internal structure, and nearby pages that may be competing for the same intent.
Should I rewrite the page as soon as a score is low?
No. A low score is a triage signal, not an automatic rewrite order. The next step is to read the evidence, check whether another page already owns the intent, and decide whether to combine, differentiate, update, or keep the page.
Why does the article mention the portal?
The public checker is useful for one URL. The portal is where full-site overlap groups, saved scan history, exports, and plan access live, so larger cleanup decisions do not disappear after one anonymous check.