Post-Publication Website Verification Checklist
Tomohiro Iida · Published August 13, 2026 · Updated August 13, 2026
A website is not fully verified when the publish button is pressed. After publication, check whether production HTML, canonicals, robots rules, structured data, internal links, forms, and GA4 events actually match the release plan. Separate implementation verification from the later observation of search and business metrics.
This article divides the checks into immediately after publication, within twenty-four hours, after seven days, and after twenty-eight days. The redesign article covers the URL map, redirects, and pre-launch baselines; this article focuses on what to inspect after the page is live.
Protect SEO, AI search visibility, and lead measurement during a website redesign
How much access to grant for web improvement
Conclusion: check whether the site can be seen, read, and measured
- Can be seen: important URLs return the intended status and redirects, canonicals, robots, and sitemap follow the release plan.
- Can be read: initial HTML, metadata, structured data, and internal links contain the intended information.
- Can be measured: CTA clicks, form starts, form submissions, and other agreed actions fire once under the right conditions.
Search rankings, inclusion in AI answers, and enquiry volume are not launch-day pass/fail indicators. Record immediate implementation checks separately from later observations because recrawling and user behaviour take time and are affected by other changes.
1. Checks immediately after publication
| Area | What to check | Evidence to retain |
|---|---|---|
| HTTP and redirects | Important URLs, old URLs, and enquiry completion pages | URL, status, final URL, Location, and check time |
| Canonical and robots | Canonical value, noindex, and robots.txt | Production HTML and policy comparison |
| Sitemap | New URLs are included and unintended URLs are absent | Fetched sitemap and release URL list |
| Metadata | Title, description, Open Graph, and language alternates | Relevant production HTML |
| JSON-LD | Article, Organization, Breadcrumb, and other relevant data | JSON-LD and validation result |
| Internal links | Navigation, CTAs, related articles, and language switchers | Link destinations and status results |
| Forms | Input, validation, submission, completion, and receipt | Test time and delivery confirmation |
Structured data can make a page eligible for search features, but valid markup does not guarantee a rich result or a particular search appearance. First confirm that the visible content and JSON-LD agree and that the markup is emitted on the intended production pages. Checked 13 August 2026 against Google’s official guidance.
Google Search Central: Ask Google to recrawl a URL
Google Search Central: Introduction to structured data
2. Check GA4 and forms within twenty-four hours
| Action | What to verify | Common failure |
|---|---|---|
| CTA click | Event name, location, destination, and one firing per click | The destination is correct but the event still uses the old specification |
| Form start | The event fires when input begins | A page view is counted as a form start |
| Form submission | The event fires only after a successful submission | Validation failures or reloads create false submissions |
| Phone and email | The agreed tel and mailto events work on desktop and mobile | Only one device type is measured |
| Download | The event represents the agreed download action | Clicks and completed downloads are treated as the same action |
Use Realtime, DebugView, and the production browser interaction as early evidence. Record the page, parameters, firing condition, consent state, and count. A named event alone is not proof that the measurement is correct. Check the official GA4 event documentation for the current event model before changing the implementation.
Google Analytics: About events
3. Check search and publication state after seven days
- Inspect representative URLs in Search Console and record the retrieved state and selected canonical.
- Check redirect errors, unintended 404s, and old URLs that should still resolve.
- Compare the submitted sitemap with the intended publication list.
- Check whether important pages became orphaned from internal links.
- Compare GA4 events and form receipts with the pre-publication baseline without treating a count difference as a causal conclusion.
URL inspection, retrieval, canonical selection, and search-result inclusion are different states. Record them separately. Search Console can help inspect the state of a URL, but it does not guarantee a search listing.
4. Evaluate changes after twenty-eight days
| Metric | Comparison unit | Record alongside it |
|---|---|---|
| Search impressions | URL, query, and device | Seasonality and other releases |
| Clicks and CTR | URL and query | Title or description changes |
| Average position | Representative query | That position is not a guarantee |
| Organic sessions | Landing page | Any measurement changes |
| CTA and form actions | Page, action, and location | Path or label changes |
| Enquiry quality | Business classification | Quality, not only volume |
Twenty-eight days is a Netsujo operating guideline, not a universal rule. Low-frequency or seasonal sites may need a different comparison period. Record advertising, new content, price changes, competitors, and search-system changes in the same evaluation log.
5. Repeat the same question when observing AI search
AI answers are not a single fixed metric. Save the question, execution time, service or model, region, answer, cited URL, errors, and changes from the previous observation. A change in an answer or citation is an observation, not by itself proof that it caused more enquiries.
6. Convert verification findings into an improvement specification
| Field | Example |
|---|---|
| Issue ID | PUB-2026-001 |
| Target URL | https://example.com/service |
| Confirmed fact | The production canonical still points to the old URL |
| Change | Set the new URL as canonical and update the template default |
| Owner | Production developer; internal web owner verifies |
| Completion criteria | Production HTML, sitemap, and internal links match the URL map |
| Next check | Immediately after the fix and again after seven days |
How to write a web improvement specification
Frequently asked questions
- Can we judge a redesign by the search ranking the next day?
- No. Use the next day for technical verification and use a predefined observation period for search and business metrics.
- Does passing a structured-data test remove the need for post-publication checks?
- No. Confirm that the markup is present on the live page, matches visible content, and is not emitted on unintended pages.
- Should a missing GA4 report be recorded as zero?
- Separate zero from not measured. Check Realtime or DebugView, the event, the report window, and the time of the check.
Key takeaways
- Check URLs, redirects, canonicals, robots, sitemap, HTML, JSON-LD, links, and forms immediately.
- Test GA4 events and form receipts within twenty-four hours.
- Use seven days for early retrieval and measurement omissions.
- Use twenty-eight days for a baseline comparison, with other changes recorded.
- Turn anomalies into target URLs, facts, changes, owners, and completion criteria.
Public information only. Identify the first URL and fact to verify after publication.
Start the Netsujo SIGNAL free diagnosisDiscuss how to divide post-publication verification, implementation, and follow-up with your existing team or production partner.
Discuss a Netsujo SIGNAL planSee the Netsujo SIGNAL service
Connect SEO and AI search work to lead measurement
How to improve a site without replacing the production company