WordPress SEO Checklist

Use this for: Public WordPress sites intended for search.

In the production dashboard, open Settings → Reading and review “Discourage search engines from indexing this site.” Clear it only when this is the public site meant for search, then save. Inspect a public page for remaining noindex from plugins or hosting. That checkbox does not secure staging or private content; use real access control for those.

1. Confirm the production address.
2. Review Settings → Reading.
3. Save the intended setting and inspect public output.

Use this for: WordPress homepage configuration.

Open Settings → Reading to see whether the homepage shows recent posts or a selected static page. For a static homepage, edit that selected page’s content and its SEO fields. For a posts homepage, use the relevant theme and SEO-plugin homepage controls. Check the public root address after saving.

1. Read the homepage assignment.
2. Edit the page or template that actually supplies it.
3. Open the public homepage.

Use this for: WordPress sites without another intentional sitemap generator.

If no plugin owns the sitemap, open /wp-sitemap.xml on your own site. Supported public WordPress core installations generate this sitemap index by default, although configuration or plugins can disable or replace it. Open a child sitemap and verify a public intended page. If the address fails, check visibility settings and installed plugins with the administrator before installing anything. Submit the working active sitemap in Search Console.

1. Open the site’s /wp-sitemap.xml.
2. Check a child sitemap and intended public page.
3. Submit the active sitemap and review processing.

Use this for: New sites or justified WordPress URL changes.

Open Settings → Permalinks and review the current structure. On a new site, choose a readable pattern such as Post name when it suits the content. Do not change an established date or category structure merely for a shorter-looking URL. A necessary change needs old-to-new redirects and updated links.

1. Review the existing structure and important URLs.
2. Choose a new-site pattern or justify a migration.
3. Test redirects and links if addresses change.

Use this for: New pages and necessary individual slug changes.

In the post or page editor, review the URL/slug control before publishing. Remove accidental draft suffixes and use a concise description of the topic. Treat changes to a published slug as URL moves: update internal links and provide an appropriate redirect rather than relying on an assumption about automatic behavior.

1. Find the draft URL field.
2. Choose a relevant readable slug.
3. Preview the address; map a redirect if the old page was public.

Use this for: Sites using Yoast SEO as the metadata owner.

In Yoast SEO → Settings, open the relevant Content types or Categories & tags screen and review the Search appearance templates. Use the page title and an appropriate site-name variable rather than one identical service phrase on every page. For an important page, edit its individual SEO title and description in the Yoast panel and inspect the final HTML after saving.

1. Review the correct content-type template.
2. Write an accurate per-page title and description where needed.
3. Save and inspect the public title and description.

Use this for: Sites using Yoast XML sitemaps.

In Yoast SEO → Settings → Site features, find the Technical SEO XML sitemaps setting and use View the XML sitemap. Open the relevant child sitemap and check a recently published, indexable page. Submit the actual active sitemap in Search Console; do not assume every WordPress installation uses the same sitemap address.

1. Open Yoast’s sitemap control.
2. Inspect the correct child sitemap.
3. Resolve unexpected omissions and check Search Console processing.

Use this for: Sites using Rank Math as the metadata owner.

Open the page’s Rank Math panel, choose General → Edit Snippet, and edit Title and Description. Review site-wide defaults in Rank Math SEO → Titles & Meta for the applicable post type or taxonomy. If a page should be indexable, inspect the published robots output for an unintended exclusion. Do not chase a focus-keyword score by repeating phrases or adding irrelevant text.

1. Edit the page snippet.
2. Review applicable template and robots settings.
3. Save and inspect the public HTML.

Use this for: Category archives used for navigation or search.

Open Posts → Categories and edit the relevant category’s name, parent and description. Assign related articles to it and check the published archive. A description saved in the category editor may not appear because its display depends on the theme. Add an appropriate archive-description element to the template when readers need that introduction.

1. Edit category fields and article assignments.
2. Open the public archive and its pagination.
3. Adjust the archive template if useful content is missing.

Use this for: Sites with taxonomy, author or date archives.

Review category, tag, author and date archives on the public site. Keep archives intended to answer a distinct browsing need available for search. If a redundant archive should stay out, use the active SEO plugin’s taxonomy/archive controls to set that intention, then inspect its robots and sitemap output. Do not noindex all categories as a default shortcut.

1. Sample each archive type.
2. Decide which serves a distinct search or browsing need.
3. Apply the relevant plugin settings and inspect output.

Use this for: WordPress themes and page templates.

For a block theme, inspect the relevant template in Appearance → Editor and the page content in its editor. Check whether the template already renders the page title as the main heading. Use Heading blocks for meaningful sections and choose their levels to show structure; do not add another prominent title solely because the editor canvas hides the template title.

1. Inspect the template’s title element.
2. Structure the page with meaningful heading levels.
3. Read the final rendered outline.

Use this for: Content images in the block editor.

Resize and compress the source image for its actual display before uploading. Insert it with an Image block, choose a suitable resolution, and set Alternative text for its purpose on that page. Media Library alt text supplies a default for future inserts; changing it does not mean every existing block has updated. Leave decorative images with an empty alternative.

1. Resize and compress while checking detail.
2. Upload, insert and choose the block’s resolution.
3. Edit this block’s alternative text and inspect mobile output.

Use this for: Sites with WordPress theme navigation.

For a block theme, open the Navigation block in the Site Editor and review links and submenus. Classic themes may expose a separate menu screen; use the menu actually assigned to the public location. Link to final live pages and test the mobile menu. Drafting a page does not automatically give it a useful place in navigation.

1. Find the active menu location.
2. Update useful links and submenu labels.
3. Test desktop and mobile navigation.

Use this for: Pages built with Elementor.

Select the Heading widget in Elementor. Under Content, edit the Title and choose the appropriate HTML Tag. Styling a widget to look large does not make it an H1. Check the theme’s page title too, then inspect the published page for the complete outline and working text links. Use the installed SEO plugin for metadata rather than expecting the heading widget to set the title tag.

1. Review the theme title and widget headings.
2. Choose semantic HTML tags in Content.
3. Publish and inspect the rendered outline and links.

Use this for: Sites with SEO plugins, custom themes or structured-data integrations.

Review active plugins and the public HTML of a post, page and archive. Identify which component generates titles, canonicals, robots directives, sitemaps and structured data. Multiple plugins can coexist, but overlapping features should not emit conflicting values. Back up and test configuration changes on a protected staging copy before removing an integration or its data.

1. Inventory overlapping features.
2. Inspect representative public output.
3. Test a narrow configuration fix before production.

Use this for: WordPress releases affecting templates, plugins or cached output.

After a template or plugin change, clear only the relevant site/CDN caches using your hosting or cache tool, then open the public page logged out. Test representative templates in PageSpeed Insights and inspect specific slow resources or layout shifts. Its field data describes real-user history when available; a fresh lab run is a diagnostic snapshot. Do not remove needed functionality merely to increase a score.

1. Check the uncached saved change on the public page.
2. Test affected templates and identify the actual resource or interaction.
3. Apply and retest a narrow performance fix.