Page types
Each a useful representative for homepage, category, detail page, guide and other important templates. Check separately for several templates.
Check and Remove Website Changes
Turn “SEO checked” into a comprehensible proof.
A release is only meaningfully checked when it is clear which pages have been examined and which requirements must be met. The website audit provides technical findings and specific references.
Automatic HTML verification as a basis. User paths and technical requirements are additionally checked.
Before the next publication
Arrange what you see as a successful change.
“SEO checked” is not very meaningful as a release note. Were the URLs tested, the canonicals viewed or just the homepage opened in the browser? Quality assurance becomes resilient if you specify in advance which properties must be correct after a change.
Describe the criteria suitable for the intervention. For a navigation exchange, link destinations are in the foreground, for a template update the SEO output and for a URL change the forwardings. A complete test catalogue is the basis; the concrete change determines your priorities.
Examples of clear criteria
- Important internal links lead to achievable, technically suitable goals.
- Public entry pages are not accidentally excluded by Noindex or Robots rules.
- Titles and H1 refer to the respective page and do not contain wildcards.
- The intended canonicals are specified in the delivered HTML.
- Contact form, navigation and other central user paths work with manual checking.
Templates and exceptions
Don’t just test the most beautiful example page.
A template can work well with a short title and fail on a long title. A product page with all data is not a sufficient test for products with missing images or unusual variants. Select your sample so that it covers the actual differences of the website.
Borderline cases
Long names, little content, distant offers, redirects or deliberately excluded pages. Document expected exceptions instead of counting them as errors.
Important introductions
Pages through which customers request or order are additionally individually controlled. Their significance cannot be read from a technical score alone.
Findings → Implementation → Control
Close the task only after the follow-up audit.
A comprehensible transfer
Record the affected URL, the observed state, and the expected result. Complete the responsible area and time of change in your existing ticket system or working document. The exports from the audit help to pass on references.
After the implementation, check the specific URL first. Then evaluate the new audit status. If the error came from a common template, you control several more pages of the same type.
Comparable measurements
Compare the scope and time of measurement. An error may seem to have disappeared because the URL was not recaptured or a quota was reached. Even a better overall score does not say whether exactly your task is done.
The agreed target state counts for the acceptance. An unchanged warning in another area does not have to speak against publication; an accidental noindex on the most important performance page can be decisive.
Continue checking after the release
Prevent the same mistake from coming back unnoticed.
After a successful release, normal operation begins again. Further editorial work and updates can change already corrected information again. Here, the regular check complements your punctual release.
Starting with an audit
The free check examines up to 20 URLs. For a more comprehensive inventory, the unlockable website audit is available. You can see results and limits in the existing range of offers.
Regularly observe the important signals
The SEO Suite offers recurring website crawls from starter. Targeted monitoring, for example for content and indexability, is included from Pro, for 39 € net per month with monthly payment, plus VAT.
The suite is not an automatic CI/CD share and does not stop release. Your team decides on the basis of the findings and the agreed criteria.
Good to know
Questions about SEO quality assurance
Can the audit automatically release a release?
No. The audit provides findings on the recorded URLs. It does not know your complete project requirements and is not an automatic deployment lock. The release remains a decision of the responsible team.
Is it enough to check the homepage?
When changing templates or navigation, several representative page types and important entries should be checked. Complement borderline cases and documented exceptions. A working start page does not occupy the condition of all subpages.
How do I document a corrected task?
Record the affected URL, previous findings, desired result and time of implementation. Complement a successful follow-up audit of the affected page and for template errors of other representative URLs. Use your existing project management for this.
Are manual tests still part of this?
Yes. An HTTP/HTML crawl does not replace an examination of interactive processes, dynamic content or technical text quality. Check central user channels, such as contact form or order, additionally in the browser.
Appropriate next steps
Prepare for the next release
- SEO crawlers
Understand the scope and findings of the website crawl.
- Monitor website changes
After a release, observe important SEO information.
- Creating SEO Reports
References and measures handed over to implementation.
- Relaunch monitoring
Accompany larger website moves in follow-up care.