Publishing is not the last writing step. It is a quality-control
event. A strong article can still lose trust through a broken button,
oversized image, misleading heading, missing disclosure, or mobile
layout problem.
This WordPress pre-publish QA checklist is intentionally practical.
It can be completed without turning every article into a technical
audit.
People may ask for this as ‘check my WordPress post before it goes
live,’ ‘why does my article look wrong on mobile?’, or ‘what should I
test before I click Publish?’ This checklist turns those broad concerns
into a repeatable sign-off process.
1. Confirm the
reader’s problem is answered
Read the introduction and conclusion without the middle. The
introduction should identify the problem and promise a realistic
outcome. The conclusion should tell the reader what to do next rather
than repeat the introduction.
Remove filler that delays the first useful information. Avoid
unsupported claims, invented statistics, and false certainty.
2. Verify the structure
- One clear H1 title
- Logical H2 sections
- H3 headings only when they belong under an H2
- Short paragraphs and useful lists
- Descriptive link text
- No empty headings or placeholder copy
Headings should help readers scan the solution. They should not be
used merely to make text larger.
3. Check facts and
instructions
Open every product page, settings page, or documentation source used
during drafting. Confirm names, menu paths, limitations, dates, and
quoted language.
For technical procedures, distinguish between universal principles
and interface details that may change. Warn readers before destructive
actions, and provide a rollback step when possible.
4. Review links
Open every internal and external link in a new test session. Confirm
that it reaches the intended destination and does not expose a private
preview, tracking dashboard, administrator URL, or personal account
information.
Affiliate links require proper disclosure. Sponsored or compensated
relationships should not be hidden behind vague language.
5. Optimize images
responsibly
Use descriptive file names, appropriate dimensions, efficient
compression, and meaningful alternative text. Decorative images should
not receive keyword-stuffed descriptions.
Confirm that images are licensed or original and do not show private
browser tabs, email addresses, account identifiers, verification tokens,
or copyrighted brand assets used without permission.
6. Test desktop and mobile
layouts
Preview the article at several widths. Look for:
- Text or buttons extending beyond the screen
- Tables that cannot be read or scrolled
- Images that dominate the opening screen
- Menus covering content
- Buttons placed too close together
- Unexpected horizontal scrolling
- Tiny text or insufficient contrast
Test the actual public preview, not only the editor canvas. Themes
and plugins can style the front end differently.
7. Check SEO essentials
SEO fields should accurately describe the content rather than chase a
score.
- Title is distinct and understandable
- Slug is short and stable
- Meta description summarizes the benefit
- Focus phrase appears naturally in important locations
- Related articles are linked where useful
- Canonical URL is correct
- Indexing is allowed for content meant to be public
Do not force awkward repetition to satisfy a plugin. A high plugin
score cannot compensate for weak or misleading content.
8. Verify trust and
compliance elements
Add an author or editorial attribution, update date when appropriate,
affiliate disclosure where required, and a correction path or contact
method.
Health, financial, and legal topics require particular care. Use
appropriate sourcing and boundaries, and do not present general
educational material as individualized professional advice.
9. Test functionality
Submit forms using a test address. Click calls to action. Test
download buttons. Check table-of-contents links. Confirm that embedded
media loads and that consent tools behave as intended.
If analytics is installed, verify that the article uses the same
single tracking implementation as the rest of the site.
10. Perform the logged-out
review
Open the preview or published article in a private window. This
catches permission problems, administrator-only elements, cache
differences, and broken public links.
After publication, repeat a shortened version of the checklist on the
canonical URL and request indexing only when the page is genuinely
ready.
A repeatable sign-off
Record the reviewer, date, page URL, and major checks completed. A
checklist is most valuable when it becomes routine rather than something
used only after a mistake.
Add a 24-hour review
for important pages
For cornerstone, commercial, or high-risk content, review the live
page again after publication. Confirm that scheduled optimization,
caching, link processing, and search metadata did not change the
presentation. Check the page from a second device when possible.
This second review often catches issues that are invisible in the
editor: clipped tables, repeated headings, delayed image loading,
missing disclosures, and buttons obscured by mobile interface
elements.
Frequently asked questions
Must every article
reach the same SEO score?
No. Plugin scores are diagnostic aids, not editorial standards.
Resolve legitimate issues, but do not degrade clarity merely to satisfy
a generalized formula.
Should drafts be indexed?
Ordinary WordPress drafts are not public. For public staging or
preview environments, confirm access controls and indexing restrictions
so unfinished or duplicate content does not enter search results.
Who should perform final QA?
The author can complete the checklist, but a second reader is
valuable for important pages. A fresh reviewer notices assumptions and
broken instructions the author may overlook.
Related guides
- Image File Names, Alt Text, and Web Performance
- Affiliate
Links Without Damaging Reader Trust - WordPress Site Recovery Checklist
Visual walkthrough
