WordPress Post-Publish SEO Checks: Preview, Public HTML and a Receipt
Tuohai editorial guide · Reviewed and published October 5, 2026. The worksheets are blank working templates, not client results.
“Post published” is a publishing response, not proof that visitors receive the approved article. The public body, canonical declaration and mobile layout still need checking at the production URL.
Post-publish WordPress QA should separate preview, public HTML and later indexing. Accept the version visitors actually receive, without turning successful publication into a ranking claim.
Start WordPress post-publish checks with the logged-out URL
Record the permanent URL, expected title, publication time and status. Draft, pending review, scheduled, private and public are different states. WordPress's Page/Post Settings documentation describes them; scheduling does not prove current public availability.
A preview can depend on login, preview parameters or unpublished revisions. Open the production URL while logged out and confirm it shows the intended article, not a login screen, password prompt, old body or error page.
For an existing article, identify the approved version through a changed heading or passage and record the check time. If old content appears, document the discrepancy before an authorized person checks publication or caching. Do not casually change the URL to demonstrate a refresh.
HTTP 200 alone is insufficient because an error page can return it. Record the production address, response and correct main body together.
Check public HTML and indexing directives
Inspect the public title, visible main heading and meta description, not just editor fields. A theme may output the title while the body adds another H1. Keep one clear main heading under this editorial specification; do not present that convention as Google's ranking threshold.
Compare important content: the introduction, technical terms, tables and source links. Saved editor content does not prove the template outputs it correctly.
Check search visibility separately. WordPress's Reading Settings documentation explains the option discouraging indexing while allowing normal visitors. Being able to open a page does not rule out an unintended indexing restriction.
Inspect HTML robots directives, Google-specific directives and the HTTP X-Robots-Tag header. Google's directive documentation supports HTML and headers and requires crawler access to read them. Checking only one location does not establish that noindex is absent.
The canonical should match the article's retention purpose. For an independently intended article, this normally means its production URL. If it points to the homepage, old host or another article, record the issue and check the template before changing tags across the site. Correct output does not prove Google's acceptance.
Check entry links, images and mobile reading
A post can be directly accessible but absent from its intended blog list or category. Follow at least one expected internal entry and check the text, destination and classification. Inspect actual sitemap inclusion rather than accepting a plugin message.
Verify public image loading, accurate alternative text and retained rights information. Do not force keywords into decorative images or portray generated visuals as real factory or test evidence. Unauthorized client screenshots do not belong in the media library or article.
On mobile, inspect long tables, URLs, headings and the action link. Desktop success does not establish readable mobile output. Record the tested size and issue location, then recheck repairs at that size.
Check that the CTA reaches the intended page and language. An accessible destination does not prove form delivery or a qualified inquiry. Contact-path investigation is separate; see the traffic-without-inquiries guide, in Chinese.
Keep a scoped publication receipt
Tuohai's October 5, 2026 public-readback and release records list checks for its transformer SEO companion page, in Chinese: HTTP 200, title, one correct H1, description, self-referencing canonical and no detected noindex.
These are historical publication-check facts from that batch, not a new test claimed here. They do not prove Google indexing, rankings, inquiries or acceptance of every website page. Keep that scope beside the receipt.
The following is a blank single-post receipt, not a completed inspection.
| Acceptance item | Actual evidence and check time | Pass/fix/not covered |
|---|---|---|
| Production URL and logged-out access | ____ | ____ |
| Editor status and public body version | ____ | ____ |
| HTTP response and correct main content | ____ | ____ |
| Title, main heading and description | ____ | ____ |
| HTML/header indexing directives | ____ | ____ |
| Complete canonical target | ____ | ____ |
| Image loading, alt text and provenance | ____ | ____ |
| Category/list entry and sitemap record | ____ | ____ |
| Mobile size and table readability | ____ | ____ |
| CTA destination, without delivery proof | ____ | ____ |
| Retest, owner and unresolved items | ____ | ____ |
“Not covered” matters. Without header evidence, do not claim all indexing directives were checked. A one-page inspection does not accept an entire template. Repair and retest access or body defects before handing over the public link.
Frequently asked questions
Is the job complete if the editor says published but the public URL is wrong?
Not as a public deliverable. Confirm the permanent link, visibility, body version and cache discrepancy. Repairs need authorization; do not overwrite unrelated pages to meet a count.
Can a green SEO plugin score replace public HTML checks?
No. It does not establish received HTML, response headers, template output or entry links. Treat it as a tool clue, not factual acceptance.
Do passing public checks prove Google indexing?
No. URL Inspection separates live testing from indexed-version information. Record later indexing independently, without a guaranteed deadline.
Conclusion: accept what visitors receive
Check the production URL and correct logged-out body, then public HTML, headers, entry links and mobile reading. Keep a scoped receipt with unresolved items and later indexing listed separately.
You can request Tuohai's free human SEO audit, in Chinese. The full human audit is free; scope, materials and scheduling are agreed separately. There is no guaranteed response time, indexing, ranking or inquiry outcome.
Sources
Read on October 5, 2026. WordPress documentation is in English; Google and Tuohai links below open Chinese pages. The publication example uses permitted public-check records, not private Search Console evidence.