The Complete WordPress SEO Checklist for 2026

Most WordPress SEO checklists are either too generic to act on or so long they become a chore nobody finishes. This one is scoped to what actually moves rankings and what you can verify yourself, in one sitting, without guessing whether a step matters. Work through it top to bottom, or use it as a recurring audit whenever you publish a batch of content or make structural changes to the site.

Each category maps to a specific part of your WordPress setup: what's in the page, how the site is built, what search engines can parse beyond the visible text, whether the site is technically sound, and whether you can actually see the results. Skipping a category doesn't just leave points on the table, it usually hides a problem in one of the others.

Doing this in a different order wastes effort. Writing perfect meta descriptions for pages search engines can't crawl, or adding schema to a page that's about to get a new URL from a redirect cleanup, means redoing the work later.

Content and metadata

This is the layer most site owners already know about, and the one most often done halfway. A unique title on every page is table stakes; the checklist below goes further into what actually differentiates pages that rank from pages that don't.

• Every published page and post has a unique SEO title under roughly 60 characters that includes the primary focus keyword near the front, not buried at the end, since search engines and readers both weight the first few words more heavily.
• Every page has a custom meta description, not the auto-generated excerpt WordPress falls back to, written as a specific pitch for why someone should click this result over the others on the page.
• Headings follow a single H1 per page with H2 and H3 used to actually structure the content into scannable sections, rather than skipped levels or headings used purely for font-size styling.
• Each page targets one primary focus keyword and a small set of related terms, checked against what the page's title, first paragraph, and headings actually say, so the on-page content matches search intent.
• Internal links from relevant existing pages point to new content within a few days of publishing, since orphaned pages with no internal links take longer to get crawled and rank.

Technical foundation

None of the content work above matters if the technical foundation is broken. This is where checklists usually get vague, so here's what to actually check and why each item matters.

• An XML sitemap exists, is submitted in Google Search Console, and only lists indexable URLs, since a sitemap full of redirects, noindexed pages, or 404s signals a poorly maintained site.
• robots.txt does not accidentally block CSS, JavaScript, or entire sections of the site that should be crawlable, which is a common mistake after a staging-to-production migration.
• The entire site serves over HTTPS with no mixed-content warnings, since browsers flag insecure content and it can affect both rankings and user trust.
• Pages render correctly on mobile viewports with tap targets sized appropriately and no horizontal scrolling, since Google indexes the mobile version of your site by default.
• Core Web Vitals pass Google's thresholds: Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1, measured at the 75th percentile of real visitor data in the Chrome User Experience Report.

Sitemap and indexing issues are the most common technical problems we see on WordPress sites that have been through a theme change, a plugin migration, or a URL structure update at some point in their history. If sitemaps and indexing haven't been checked recently, that's worth doing before anything else on this list.

Structured data

Structured data doesn't change what a page says, it changes how clearly search engines and AI systems understand what the page is about. This is the layer most WordPress sites skip entirely, or implement inconsistently across post types.

• Sitewide Organization or WebSite schema is present with correct name, logo, and URL, giving search engines a baseline entity to associate with every page on the site.
• Article schema is applied to blog posts and includes headline, author, publish date, and modified date, all of which need to match what's visibly on the page.
• Content-specific schema types, FAQPage, HowTo, Review, or Product, are added wherever the content actually matches that format, rather than applied generically across unrelated pages.
• Schema validates without errors in a structured data testing tool, since a single malformed property can cause the entire block to be ignored.

If you're implementing this by hand with JSON-LD in a functions file, our schema markup guide for WordPress walks through the specific types worth prioritizing. Rankwyn's schema and structured data feature publishes foundation schema automatically and lets you add FAQ, HowTo, and review blocks without writing JSON-LD by hand.

Site health

Site health issues accumulate quietly. A redirect chain from three URL structure changes ago, a broken outbound link in a post from two years ago, none of it breaks the site visibly, but it erodes crawl efficiency and user trust over time.

• Redirects use a single 301 hop rather than chains of two or three redirects stacked on top of each other, since each additional hop adds latency and dilutes link equity.
• A crawl of the site turns up no unintended 404 errors, and any that do exist are either fixed or redirected to a relevant live page rather than left to return a dead end.
• Outbound links to external sites are checked periodically for link rot, since a page full of dead external links reads as unmaintained to both readers and search engines.

This category is the one most likely to get skipped because none of it is visible in the editor. Rankwyn's site maintenance tools run this kind of check on a schedule instead of relying on someone remembering to do it manually.

Measurement

A checklist without measurement is a one-time exercise. The point of tracking these numbers is knowing whether the work above actually changed anything, and catching regressions before they compound.

• Google Search Console is connected and verified for the property, with the sitemap submitted and indexing coverage checked for unexpected drops.
• Keyword rankings for the site's priority terms are tracked on a recurring basis, so a ranking drop gets caught within days rather than discovered months later when traffic has already fallen.

None of these five categories work in isolation. A page with a well-optimized title and clean schema still won't rank if the sitemap never submitted it. A technically sound site with no metadata strategy won't convert clicks even when it does rank. Treat this as one system, not five separate to-do lists, and revisit it whenever the site changes meaningfully rather than once and never again.

It also helps to know where to stop. Perfecting every meta description on a 200-page site before fixing a broken sitemap is a common way teams burn a week on the wrong priority. Work the categories in the order the audit flow above lays out, technical foundation before content polish, structured data after both are stable, and treat measurement as ongoing rather than a step you finish once. A checklist that's 80 percent done in the right order beats one that's 100 percent done in the wrong order, because the wrong order means redoing content work after a URL structure fix breaks the links you just built.

For a full breakdown of what Rankwyn handles end to end, see pricing for plan details.