A practical workflow to review SEO changes before publishing: sitemap, link relationships, redirects, keyword usage and structured data.
Publishing a page, migration or template change can affect several SEO signals at once. A useful pre-publish audit does not try to predict rankings; it checks whether the technical output matches what you intended to deploy.
The most reliable approach is to compare before and after, then inspect the specific elements that changed.
A sitemap change can reveal URLs that disappeared unexpectedly, new URLs that should not be indexed or path changes introduced by a migration.
The sitemap diff tool compares two sitemap states so additions and removals are easier to review.
A sitemap is a discovery signal, not a guarantee of indexing. The audit question is whether it contains the canonical, indexable URLs you intended to expose.
Links can carry attributes such as nofollow, sponsored, ugc, noopener or noreferrer. These attributes serve different purposes and should reflect the relationship and behavior intended for each link.
The link rel analyzer helps inspect these values in markup.
The goal is not to add attributes mechanically to every link, but to detect accidental or inconsistent markup.
When an existing URL changes, a redirect can preserve navigation and tell crawlers where the resource moved.
The redirect rule generator helps prepare rules for supported server formats. Generated configuration should always be reviewed in the context of the actual hosting stack.
Check for:
The keyword density analyzer can show how frequently terms appear in a text.
That information is descriptive, not a target score. There is no universal percentage that guarantees better rankings. Use the result to detect awkward repetition, missing terminology or accidental template duplication rather than to force a particular density.
Readable, useful content should remain the priority.
Structured data must be syntactically valid and should accurately describe content that is actually present on the page.
The structured data validator helps inspect JSON-LD and identify structural problems before deployment.
Validation alone does not guarantee eligibility for a search feature. Search engines apply their own guidelines and may change how features are displayed.
This workflow complements a broader technical SEO checklist. Its purpose is simple: catch implementation mistakes before they become production crawl problems.
Collection
7 / 7
Design stable readable URLs, normalize slugs and parameters, and reduce duplicate or ambiguous public routes.
Understand crawling, indexing, canonicals, metadata, structured data, performance and internal linking without confusing optimization with ranking.
Understand structured data, choose relevant Schema.org types and generate JSON-LD that matches visible page content.