09 / Quality assurance
This page defines 18 SEO Monitoring & QA terms. Each entry gives a plain definition, a What to check step you can apply to your own site, and links to deeper SiteAuditLint guides where they exist.
SEO audit
An SEO audit is a structured review of a site's technical health, content, and links to find issues limiting search performance.
Prioritize findings by impact and affected templates, rather than fixing every flagged warning equally.
How often should you do an SEO audit?
A full audit once or twice a year is common, but critical technical checks should run continuously or with every release.
Go deeper: Site audits course, SEO audit checklist
Rank tracking
Rank tracking is monitoring where your pages rank for a defined set of keywords over time, by location and device.
Track the same keywords, locations, and devices consistently, and record SERP features alongside positions.
Ranking volatility
Ranking volatility is how much search rankings fluctuate over a period, across your site or across the whole SERP.
Compare your movement with industry volatility trackers to tell site issues apart from algorithm changes.
Visibility index
A visibility index is a single score estimating how visible a site is in search for a keyword set, weighting rankings by position and search volume.
Investigate which keywords and pages drove a visibility change before reporting the headline number.
Baseline
A baseline is a recorded snapshot of normal performance, such as rankings, indexed pages, or traffic, used to compare future changes against.
Capture a baseline before every migration, redesign, or major release.
Go deeper: Audit comparison
Historical comparison
Historical comparison is comparing current SEO data with earlier periods to identify trends, regressions, and seasonality.
Compare year over year as well as period over period, so seasonal patterns are not mistaken for problems.
Go deeper: Scheduled SEO audits
Change detection
Change detection is automatically identifying changes to SEO-critical page elements, such as titles, canonicals, robots directives, or content.
Monitor high-value templates for unexpected changes, especially after deployments by other teams.
Go deeper: SEO change management
Log file analysis
Log file analysis is reviewing server logs to see exactly which URLs search engine and AI crawlers request, how often, and what status codes they receive.
Compare crawler hits with your important URLs to find wasted crawl activity and pages bots rarely visit.
Go deeper: Track AI crawlers with Cloudflare
SEO monitoring
SEO monitoring is the ongoing tracking of rankings, traffic, indexing, and technical health to catch problems early.
Define thresholds that matter, such as a drop in indexable pages, instead of reviewing dashboards manually.
Go deeper: SEO monitoring
SEO alerting
SEO alerting is sending automatic notifications when monitored metrics cross defined thresholds, such as a spike in 5xx errors or a removed canonical.
Tune alerts so they fire on real risks, since too many low-value alerts get ignored.
Go deeper: Slack SEO alerts
Staging environment
A staging environment is a non-public copy of a site used to test changes before they go live.
Block staging from indexing with authentication, and confirm staging noindex rules are not pushed to production.
Go deeper: Website launch SEO checklist, Pre-launch website checklist
Pre-deployment check
A pre-deployment check is an SEO review run on staging before a release, to catch issues before they reach the live site.
Test titles, canonicals, robots directives, status codes, internal links, and structured data on changed templates.
Go deeper: Pre-deployment SEO testing
Post-deployment check
A post-deployment check is an SEO review run on the live site immediately after a release, to confirm nothing broke in production.
Re-crawl key templates, compare with the baseline, and check robots.txt and XML sitemaps.
Go deeper: Post-deployment SEO testing
Deployment checks
Deployment checks are the combined set of pre-deployment and post-deployment SEO tests built into a release process.
Make deployment checks part of the release checklist, so SEO review does not depend on someone remembering.
Go deeper: SEO QA checklist
Regression testing
Regression testing is re-testing existing functionality after a change to make sure nothing that previously worked has broken. In SEO, it covers technical signals that releases can accidentally change.
Keep a list of SEO-critical elements per template and test them automatically on each release.
Go deeper: SEO testing course
SEO regression
An SEO regression is a change that unintentionally harms search performance, such as a lost canonical, an accidental noindex, or broken internal links.
When traffic drops, check release dates first, since regressions often line up with deployments.
How do I prevent SEO regressions?
Run automated SEO checks before and after each deployment, compare results with a baseline, and alert on critical changes.
Go deeper: SEO regression checklist, SEO incident investigation
Technical SEO validation
Technical SEO validation is confirming that technical SEO requirements are correctly implemented, such as redirects, canonicals, hreflang, and structured data.
Validate against the rendered page and live response headers, not only the source code or CMS settings.
Go deeper: SEO acceptance criteria
SEO evidence
SEO evidence is the documented data proving an SEO issue, fix, or impact, such as crawl results, screenshots, logs, and before-and-after comparisons.
Save evidence with dates and URLs for every significant fix, so results can be explained to stakeholders and repeated.
Go deeper: SEO evidence: how to prove an SEO finding is real
Browse the full SEO terms glossary, or run a technical SEO audit with SiteAuditLint to check these signals on your own site.