Use this WordPress SEO checklist as a release and maintenance record. Every important check should have a URL, observed evidence, owner, priority and retest result. A tick should mean someone inspected the intended output, not merely that a plugin reports a passing score. Our order is public access first, accurate discoverable content next, and a working business path throughout.
Fact-checked as of October 22, 2026. Published by Citera. These are our proposed acceptance checks informed by linked official documentation. This is not a report of an audit performed on your website, a connected WordPress test or a guarantee of indexing, ranking, AI citations or revenue. Any changes need the appropriate owner’s approval.
Cover: illustrative architecture from Unsplash, not a screenshot of a completed audit.
Create an evidence register and representative sample
Record the production domain, hosting arrangement, WordPress environment, theme/editor, SEO plugin, release owner and date. Include intended markets, languages and the main enquiry, signup or purchase path. Separate staging from production in the register rather than assuming a check on one applies to both.
Our suggested sample contains the homepage, a commercial page, an ordinary post, a long-title post, a category or tag archive and a secondary-language page where relevant. Add the page-builder, custom-field or commerce templates the business actually relies on. An audit of one attractive page is not coverage of every template.
Check record | What belongs in it | Pass standard |
|---|---|---|
Environment | Domain, host, release date and owner | Intended public destination identified |
Affected content | Exact URL, item or template | Sample and unsampled scope explicit |
Observation | Response, output, screenshot or report | Evidence answers the check |
Action | Owner, priority and approved change | No unexplained or unapproved mutation |
Retest | Date, result and remaining limitation | Pass, Fail or Pending is accurate |
Our suggested priorities are blocking access or business actions first, systematic template problems next, then lower-impact cleanup. Preserve pending evidence instead of converting it into zero issues.
Check hosting, public access and the active sitemap
Environment: identify WordPress.com versus self-hosted WordPress and the host’s responsibilities. Do not assume the same backups, staging or access controls from the platform name. 1
Public target: open representative production URLs without dashboard access. Record actual response, redirect and final destination. A working editor preview is not this test.
Indexing setting: inspect Reading settings and effective production directives. “Discourage search engines” is not access protection. 2
HTTPS and redirects: inspect the intended host/protocol and relevant old URLs. Record unexpected chains, loops or destinations; keep the previous mapping before an approved change.
Sitemap owner: identify the active sitemap rather than assuming every site uses the same filename. Core provides a sitemap implementation, but the actual installation can be customized. 3
Host/CDN policy: investigate an exact crawl-access failure with the technical owner. Do not globally disable security protections to satisfy a generic audit.
Pass for the URLs actually inspected. List excluded templates, private content and unresolved hosting questions. Treat being present in a sitemap as discovery evidence, not proof that a search engine indexed the page.
Check canonical, archive and duplicate-content decisions
WordPress core outputs a canonical for singular queries. 4 Our check inspects the final canonical on each sampled page and identifies which layer owns it. Confirm it describes the intended production URL rather than staging, a different article or an unexplained parameter version.
Write a deliberate policy for categories, tags, authors, pagination, internal search and parameter URLs. Our checklist does not prescribe blanket noindex for every archive. The right decision depends on whether that page has a useful maintained purpose and how the website is organized.
Find articles that answer the same buying question without a useful distinction. Record the proposed retained page, necessary content merge, internal-link changes and redirect decision before changing anything. Avoid creating another page solely by replacing SEO with AEO or GEO in the title.
For changed slugs, test the old URL, expected destination, final status and important query behavior. Keep a route map and named owner. A broad homepage redirect is not automatically an acceptable substitute for a relevant maintained answer.
For multilingual pages, verify the actual locale URL, language, canonical and relevant alternative-language signals with the implementation owner. Do not guess a locale path from a translated title or assume a primary-language audit covers all markets.
Check metadata and factual schema ownership
Our pass standard is agreement between visible page facts and emitted metadata or structured data. Record one intended owner for overlapping SEO output. Choose configuration deliberately rather than adding multiple plugins to make an unexplained warning disappear.
Yoast documents a connected schema approach; Rank Math documents its own SEO and schema controls. 5 6 This is not evidence that either product’s default configuration matches every business or custom template.
Inspect an ordinary article, sparse item, long title and commercial page. Check meaningful titles and descriptions, actual author identity, date semantics, appropriate images and visible factual support. Fail placeholder content, invented reviewers or ratings, and contradictions between the body and markup.
If the site uses plugin-generated and custom-code schema, investigate duplication or disagreement. Validate the intended output and retain evidence. Syntax alone does not establish that the marked-up facts are true.
Google does not require special AI schema or a new AI text file for its AI search features. 7 Do not add unverified markup merely to claim GEO completeness. A technically eligible page is still not guaranteed inclusion.
Check content, media, links and accessibility
Read the sampled page as a buyer. Our checks are a direct answer, appropriate detail, accurate claims, current source links and an understandable next action. A long article is not automatically a useful one. Confirm that caveats remain visible rather than being removed from the summary that a buyer actually reads.
Inspect heading order, paragraphs, native lists, table headers and link names. Test long headings and comparison tables on desktop, tablet and phone. Pass when important text is readable without document-wide sideways scrolling and keyboard focus can reach the relevant actions.
Check images after they enter view: load success, meaningful alternative text, appropriate sizing and provenance. WordPress’s media resource exposes alt text and other image data. 8 A successful upload is not proof that the theme renders the right information.
Follow contextual links and the primary conversion path. For this Citera series, signup links should reach app.citeralabs.ai/signup, while demo links should reach the existing booking page. Stop before submitting real prospect data unless a sanctioned test explicitly authorizes it.
Dismiss optional cookie and promotional interfaces, close dialogs and verify that navigation and the footer remain usable on phone. Record a blocked action with its actual cause rather than reporting that a button works because its URL looks correct.
Check permissions, supported fields and controlled publication
Document the intended writer, reviewer and publisher. WordPress roles have different capabilities; a Contributor is not equivalent to an Editor. 9 Use permissions meeting the actual integration requirement instead of granting broad administration by habit.
For a remote content connection, use the supported authentication route. WordPress supports Application Passwords over HTTPS. 10 Keep credentials out of public content, browser-side code and evidence screenshots.
Citera’s WordPress guide distinguishes its connection routes and identifies manual treatment for page-builder/custom-field content. 11 Confirm ordinary post fields, SEO-plugin metadata, custom post types, locale data and WooCommerce requirements individually. Mark untested targets as not verified, not automatically supported.
Run one approved draft through the intended process. Check the destination, author, body, images and chosen publication state. Citera documents several approval policies. 12 Verify the configured policy before scaling an unattended workflow.
Record a correction and rollback plan. WordPress revisions can compare or restore saved content, with retention depending on configuration. 13 Keep a separate host-appropriate backup plan for wider changes, and do not assume disconnecting a service deletes already-published posts.
Check search evidence and completed business actions separately
Ask the authorized Search Console owner to inspect representative production URLs. The indexed view and live test are different evidence; a live test does not prove appearance in search or predict the selected canonical. 14
Our event register distinguishes page view, signup-link click, completed signup, demo-link click, confirmed booking and qualified enquiry. Name the receiving property, consent state, event definition and responsible application or booking owner. A website click is not a downstream completion.
Citera documents connections to Search Console, GA4 and Bing. 15 Check the actual receiving reports and agreed source definitions. Do not claim perfect AI attribution, assign unknown traffic to AI or treat a missing owner check as a verified result.
For sampled AI visibility, preserve the prompt, engine, language, market, observation date and citation URLs. For crawl evidence, keep bot requests separate from human visits. OpenAI distinguishes its search crawler from its training crawler. 16 Counting either is not counting a customer.
Our release can pass website checks while downstream account or commerce evidence remains pending with an owner. State that boundary plainly instead of inventing a complete revenue report.
Approve the release and assign maintenance
Before publishing, list approved items, fields, templates, languages and domains. Review unrelated staged work and preserve it. After release, inspect the public URLs again, including important images, metadata, internal links and CTA destinations. Keep the resulting version and evidence with the audit record.
Assign ongoing ownership for content accuracy, plugin/theme compatibility, access, broken links and meaningful conversion events. Retest after relevant migrations or template changes, not just on the date a tool sends a report. Keep the first recurring scope small enough that somebody will actually complete it.
Our release fixture set makes that retest concrete. These are recommended checks, not assertions about a site we inspected:
Fixture | Acceptance question | Evidence retained |
|---|---|---|
Long-title post | Does the heading, card, metadata and phone view remain readable? | Public URL and responsive screenshots |
Missing optional cover | Is there an intentional, accessible layout rather than a broken image? | Final output and media decision |
Existing article correction | Are the approved caveat, author, sources and intended URL preserved? | Before/after record and reviewer approval |
Category or author archive | Does it have the intended purpose, links and indexability policy? | Rendered page plus agreed technical policy |
Custom-field or builder page | Is the actual content source supported and the manual work assigned? | Field contract and verified public result |
Secondary-language page | Do the answer, locale URL and conversion destination match the market? | Language review and public routing evidence |
Signup, enquiry or demo link | Does navigation reach the intended destination without an obstructing overlay? | Observed destination; completion evidence kept separately |
A site owner should be able to hand this record to a different reviewer and obtain the same understanding of what was checked. If a fixture is not relevant, record why; if it is relevant but untested, retain Pending. Reproducibility is more useful than an impressive-looking “100% SEO” label with no identifiable sample. Use the failed fixtures to determine the next contained change and the person responsible for verifying it.
Do I need a more expensive WordPress.com plan just for plugins?
Current documentation permits plugins on every paid plan. Other hosting features and compatibility still need their own check. 17
Should I pass every automated recommendation?
No. Investigate the affected output, decide whether the recommendation fits the site, approve a contained change and retest. A tool score is not a substitute for public-page evidence.
For a tool decision, read Best SEO Tools for WordPress or Best GEO Platforms for WordPress. For a first implementation, use How to Optimize a WordPress Website for AI Search and the WordPress hub.
Start free to explore Citera, or book a demo to map your audit findings, supported CMS workflow and review responsibilities.
