WordPress SEO Settings Checklist: A Step-by-Step Guide

Most WordPress SEO settings live in a handful of admin screens long before any plugin enters the picture: General, Reading, Permalinks, Discussion and the media tools. One checkbox ticked at the wrong moment can keep an entire site out of search results, and one badly chosen URL structure can leave you with address problems you carry for years. This article is a screen-by-screen WordPress SEO checklist for small business owners and bloggers, built on WordPress's own documentation and Google Search Central guidance rather than on folklore.

The goal is not to push you toward a particular plugin or brand. It is to show where to look in your own installation, what to change and why, and how to confirm that the change actually did what you expected. Screen names shift slightly between versions, themes and language packs, so each step gives you both the menu path and the thing to look for. One caveat up front: none of these settings guarantees rankings, traffic or indexing. The checklist helps you find and remove obstacles, nothing more.

Before You Touch Anything: Backups, Scope and Verification

Back up first, then change settings

Permalink, site address and visibility settings change how a live site behaves the moment you save them. If you are editing an established site, take a full backup first or rehearse the changes on a staging copy. A brand-new site that has not launched carries less risk, but following the order below still makes it easier to tell which change caused which effect.

Core settings versus plugin settings

This guide covers settings that ship with WordPress itself. The final HTML your visitors and crawlers receive, including the title tag, description, canonical link and sitemap, is produced by WordPress core together with your theme and any installed plugins, and which of them outputs what differs from site to site. That is why every section ends with something to check in the page source. Comparing plugins is outside the scope of this article; whichever one you use, the questions and the verification steps stay the same.

Plan the verification

After each change, check the same three things: whether the expected tag appears in the page source, whether the relevant URL opens in a browser, and whether Google Search Console reports an error for it. Search Console adds detail but is not instant, so treat your own page-source check as the primary evidence and Search Console as the second opinion.

General Settings: Site Title, Tagline and Site Address

Site title and tagline

Open Settings, then General. According to the WordPress documentation, the site title is what most themes show at the top of every page and in the browser title bar, and WordPress also uses it as the identifying name of your syndication feeds. The tagline is meant to describe in a few words what the site is about, and its default value is an empty string. Together they define your brand name and one-line description, so replace any placeholder text left over from installation with your real name.

There is no single correct tagline. A short, accurate sentence is enough, and stuffing it with keywords helps neither readers nor search engines. Google's SEO Starter Guide says a good title is unique to the page, clear and concise, and accurately describes the page's contents. Because many themes append the site title to every page title, a long or repetitive site name lengthens every title on the site.

WordPress Address and Site Address

The same screen has two address fields. The documentation defines the WordPress Address as the location of the directory holding the core application files, and the Site Address as the address people type into a browser to reach your site. Unless you installed WordPress in its own directory, the two are identical. Both should be consistent and should reflect the form you prefer: https, and with or without www.

Google's documentation on consolidating duplicate URLs says Google generally prefers the HTTPS version of a page over the HTTP one, suggests redirecting HTTP to HTTPS, and warns against invalid certificates and HTTPS-to-HTTP redirects. Entering your address as https and keeping the certificate healthy is therefore a foundational setting. The same page gives no explicit preference between www and non-www; what matters is picking one and making every internal link, redirect and sitemap address agree with it.

Checkpoints for this section

• Does the site title carry your real brand name, with no sample text left behind?
• Is the tagline short and accurate, or deliberately empty?
• Does the Site Address start with https, and does the browser show no certificate warning?
• Does the old http address permanently redirect to the new one?

Reading Settings: The Search Engine Visibility Checkbox and Your Homepage

What the discourage-indexing option actually does

This is the single most damaging checkbox among all WordPress SEO settings. You find it on the Reading screen under search engine visibility. The WordPress documentation (Opens in a new tab) says that ticking the box asks search engines not to index the site, and that since WordPress 5.3 it causes a robots meta tag with noindex and nofollow values to be added to the head of your pages. The same page stresses that the option does not block access to the site: it is up to search engines to honor the request.

The documentation lists side effects too: ping notifications stop, and the Update Services option is hidden from the Writing screen. The core sitemap announcement adds that sitemaps are disabled when the visibility setting discourages search engines. One checkbox therefore touches the meta tag, the sitemap and the notifications all at once.

Why it gets left on, and how to spot it

The box is often ticked on purpose during development, because nobody wants a half-built site in the index. The trouble starts when the site goes live and the box stays ticked. The check is simple: confirm the box is empty on the Reading screen, then open a post's page source and search for the robots meta tag. If you see noindex there, either the box is still ticked or your theme or a plugin is emitting a noindex of its own. In both cases the launch is not finished until you know where it comes from.

Google's noindex documentation (Opens in a new tab) explains that the rule can be delivered in a meta tag or an HTTP header, and that the page must not be blocked by robots.txt or Google will never see the rule. You therefore cannot block a page in robots.txt and also expect noindex to work on it. Our noindex tag and X-Robots-Tag guide goes deeper on the mechanics.

Homepage and posts page

The top of the Reading screen lets you choose whether the front page shows your latest posts or a static page. According to the documentation, the homepage and the posts page cannot be the same page, and if you pick a static front page without choosing a posts page, your posts are reachable only through other navigation such as categories and archives. A company site often reads more clearly with a static homepage and a separate blog page, while a pure blog can keep the latest posts on its front page. Decide by user journey rather than by SEO folklore: what is the visitor looking for, and where do they start?

While you are on this screen, look at how many posts each listing page shows. The number controls how long your archive pages are. Very short lists create many pages, and very long lists may load slowly. There is no universal figure; test your theme on mobile and judge by load time and readability.

Permalinks: Choosing a URL Structure You Can Live With

The options and what they mean

The Permalinks screen under Settings decides how post and page addresses look. WordPress's documentation introduces the common settings with example addresses, summarized in the table below.

Which structure suits SEO?

Google's URL structure documentation recommends readable words over long ID numbers, hyphens rather than underscores to separate words, and picking one letter case because paths that differ only in case count as different URLs. The SEO Starter Guide adds that URLs made only of random identifiers are less helpful to users, while keywords in the domain or path have little ranking effect beyond breadcrumbs. A readable structure such as post name is therefore reasonable for most sites, but do not expect a ranking boost from it. The benefit is readability and maintainability. For slug-writing principles, see our guide to URL structure and slug best practices.

If you choose post name, you can shorten the final address segment (the slug) of every post by hand. Test how your language's special characters appear in the slug on the first post you publish. WordPress normally generates the slug from the title, but seeing the result before publishing is your job.

Changing permalinks on a live site

The documentation opens by saying a post's URL should be permanent and never change, hence the name permalink. That sentence describes the risk of changing a structure after launch. Once you do, old addresses may not automatically point to the new ones, so before saving on a live site, build a map of old and new addresses and set up permanent redirects (301 or 308). Google's redirects documentation recommends permanent server-side redirects whenever possible and says Google uses them as a signal that the target should be canonical. The workflow in our new website launch SEO checklist gives you a pattern for testing redirects.

The documentation also explains that you must click Save Changes for a new structure to take effect, and that if your .htaccess file is not writable, WordPress shows you rewrite rules to copy by hand. It adds that merely visiting the Permalinks screen flushes the rewrite rules, with no need to save. If an address returns a 404 after a change, visiting this screen is a sensible first step.

Category base and tag base

An optional section on the same screen lets you enter custom prefixes for category and tag URLs. The documentation's example turns the category base into a topics directory. Leave the fields blank and defaults apply. Fill them only when you have a real need, and remember that changing them on a live site changes every category and tag address.

Sitemaps: WordPress's Built-In Map and What to Check

What the core sitemap produces

WordPress 5.5 added basic XML sitemap functionality to core. According to the announcement, the sitemap index is served at wp-sitemap.xml, and by default it covers public, publicly queryable post types, taxonomies, author archives and the homepage. The post also says each sitemap holds up to 2,000 entries by default (a value that can be filtered), that the feature can be switched off with the wp_sitemaps_enabled filter, and that WordPress's robots.txt output references the sitemap index. A commenter reported not seeing that reference and a maintainer replied that it happens automatically, so open your own /robots.txt and confirm.

Your theme, a plugin or your host may also publish a sitemap of its own. If two sitemaps exist, decide which one is authoritative, disable the other, and submit only the authoritative one to Search Console.

Do you even need a sitemap?

Google's sitemap documentation (Opens in a new tab) says that if your pages are properly linked, Google can usually find most of your site without one. It describes sites of about 500 pages or fewer with comprehensive internal linking as ones that may not need a sitemap, and notes that platforms such as WordPress likely already provide one. It also stresses that a sitemap aids discovery but does not guarantee that every listed URL is crawled or indexed. So do not worry that a sitemap exists; worry when it reports the wrong things.

Keeping the sitemap consistent with everything else

A sitemap should list only canonical, public addresses you want indexed. A noindex page inside the sitemap is a contradictory signal, and so are redirected or 404 addresses. You can follow the audit steps in XML sitemap audit and error fixes. Remember the Reading checkbox from earlier, too: if the sitemap vanishes, that is the first place to look.

Canonical, Noindex and Archive Pages

Who outputs your canonical tag?

The same content can be reachable under several addresses: parameter variants, versions with and without a trailing slash, category and tag paths. Google's documentation (Opens in a new tab) calls rel canonical a strong signal about which URL should be canonical and recommends adding a self-referential canonical on the canonical page itself. It also asks you to link to the canonical URL, not to a duplicate, when linking within your site. If you do not know whether core, your theme or a plugin outputs the tag, search the page source for rel canonical: there should be exactly one, it should point to the right address, and it should match the page's own address. For typical failure patterns, use canonical tag issues, audit and fixes.

Noindex versus robots.txt

Google's introduction to robots.txt says the file is used mainly to avoid overloading your site with requests and is not a mechanism for keeping a page out of Google; to do that, block indexing with noindex or password-protect the page. For pages you want out of the index, use noindex in the page source or an HTTP header. If you also block the page in robots.txt, Google cannot see the noindex rule. This one principle prevents a very common WordPress mistake: disallowing login or thank-you pages in robots.txt and then adding noindex to the same pages.

Archives, tags and attachment pages

WordPress generates category, tag, author and date archives. Whether those should be indexed is an editorial decision tied to your content structure, not a rule. On a blog, a category page can be a useful list for readers. On a single-author site, the author archive may behave like a copy of the homepage. Ask whether the page offers anything original or just reshuffles the same posts, and judge weak pages one by one rather than applying a blanket rule.

If you decide to noindex some archives, remove them from the sitemap too and do not block them in robots.txt, otherwise Google cannot see your decision. Themes and plugins usually expose these options per taxonomy or content type. After changing them, confirm the expected robots meta tag in the page source.

Titles, Descriptions and Heading Structure

The title element

Google generates title links from the title element and other headings on the page. The SEO Starter Guide says a good title is unique to the page, clear and concise and accurately describes the page's content, and notes that most content management systems turn the title you write into the title element automatically. In WordPress, your theme decides how the page title and the browser title combine, so look at one post's source to see whether the site name is appended. Duplicate titles across pages and empty or default titles are the usual flaws.

Meta descriptions

The same guide explains that snippets are mostly built from the page's own content, that Google occasionally uses the meta description instead, and that a good description is short, unique to the page and includes its most relevant points. WordPress core has an excerpt field, but whether it serves as the meta description depends on your theme and plugins. Verify where the description comes from yourself, and start with the pages you expect to attract the most visits instead of writing every description at once.

Heading hierarchy

Most themes print the post title as the H1, and you continue with second-level headings inside the post. Some themes also wrap the logo or site name in an H1, producing more than one on a page. That is often not a disaster, but a clean structure serves readers and screen reader users. For details, see heading structure for SEO and accessibility.

Images and Media: Alt Text and File Preparation

Where to enter alt text

The WordPress Image block documentation describes an alternative text field: you add meaningful alt text, or mark the image as decorative when it adds no information. Alt text entered in the Media Library becomes the default whenever you insert that image again, while alt text typed into the block settings affects only the image on that page. Google's SEO Starter Guide defines alt text as a short but descriptive text that explains the relationship between the image and your content, and says it helps search engines understand the image.

The documentation also notes that many devices and browsers do not display the title attribute, so never put important information only there. Instead of stuffing alt text with keywords, write it as if describing the picture to someone who cannot see it. For wider image principles, read our guide to image SEO and optimizing images for Google.

Preparing files before upload

Before uploading, resize the image to the size you need, give it a meaningful file name and avoid needlessly large files. Heavy images affect page speed directly, and the broader effect on page experience is covered in our page speed and Core Web Vitals guide. If you use screenshots, make sure the text is readable and, where it matters, give the same information in text as well.

Internal Links and Comment Settings

Internal links

Internal links help readers move around your site and help crawlers find new pages. Google's SEO Starter Guide says link text tells both users and Google something about the page it points to, so describe the destination instead of writing "click here". When you publish a new WordPress post, add two items to your publishing checklist: older posts that could link to it, and related pages it should link out to. Our piece on internal linking strategy and SEO impact covers the approach.

Comments and outbound links

The Discussion screen under Settings controls whether comments are allowed, whether commenters must give a name and email, and whether comments need approval. According to the documentation, you can hold a comment in the moderation queue if it contains a set number of links or more, since many links are a common sign of comment spam. Spam hurts both site quality and reader trust, so choose your moderation settings deliberately.

Google's documentation on qualifying outbound links describes the ugc value for user-generated content such as comments and forum posts, the sponsored value for advertisements and paid placements, and nofollow for cases where neither fits. Check your own page source to see which rel value your theme or plugins give to comment links, rather than assuming what core does.

The Step-by-Step WordPress SEO Checklist

One table for the whole workflow

The table below gathers every step in this article. The columns show where the setting lives, what to do and how to verify it.

Verification steps after launch

Once the settings are done, work through this sequence:

1. Open the homepage and at least one post in a private window and confirm the page source has no noindex.
2. Open the robots.txt address and make sure nothing that should be crawlable is blocked.
3. Open the sitemap address and look for redirected, noindex or 404 entries.
4. Compare one post's canonical address with its permalink.
5. Verify the property in Search Console, submit the sitemap and inspect a few key URLs.
6. After a few days, read the page indexing report for exclusion reasons.

A broader pre-launch and post-launch flow is in the launch checklist for a new site. The point worth stressing is that these checks are not a one-off: repeat them after theme changes, plugin updates and migrations.

Common WordPress SEO Mistakes

Leaving the visibility box ticked

The heaviest mistake is going live with the discourage-indexing box still ticked. The symptom is a noindex tag in the page source and pages missing from the index. The fix is to untick the box and then re-inspect the affected URLs in Search Console. Nobody can promise how quickly Google will recrawl and reindex; you can only fix the cause and monitor.

Changing permalinks without redirects

The second most common mistake is changing the permalink structure on a live site and not redirecting the old addresses. Inbound links and bookmarks then land on 404 pages. The fix is to map old to new and set permanent redirects. If at all possible, avoid making that change in the first place.

Two sitemaps, two canonicals, two noindex rules

Core, theme and plugins can each output the same element independently. If your source shows two canonical tags, two robots meta tags or two separate sitemaps, find the origin of the conflict. Conflicting signals leave it unclear which one Google will follow, so every output should have a single source.

Combining robots.txt and noindex

If you block a page in robots.txt while expecting noindex to work, Google cannot see the noindex. For a page you want out of the index, allow crawling and add noindex. Use robots.txt blocking only for sections where being crawled is the problem and appearing in the index is not.

Believing myths

Plenty of folklore surrounds meta keywords, domain age and similar topics. We sorted what Google's documentation actually supports in SEO myths and what Google documentation says. Configure WordPress according to documented behavior, not according to a myth.

Using SEO Plugins Without Creating Conflicts

What a plugin does and does not do

Many SEO plugins offer title templates, meta description fields, sitemaps, canonical controls and robots meta options. This article neither recommends nor compares any specific plugin; claims about a brand should come from that plugin's own documentation. The general principle is that a plugin is a tool and does not guarantee the settings are right. Never assume it works until you have checked its output in the page source.

Avoiding overlaps

When several plugins manage the same area, their output can collide. When you replace one, check how it migrates the old settings, where the old data stays and which options the new one switches on by default. After any plugin change, rerun the post-launch verification steps above. If your plugin generates structured data, our Article and FAQ schema markup guide shows how to validate the result.

Start simple

For a small blog or business site, the best start is usually to get the core settings right, publish good content and keep the user journey clear. Add a plugin later if a real need appears. Fewer settings mean fewer ways to get things wrong.

After the Settings: Content and Routine Maintenance

Settings are the floor, content is the work

A correctly configured WordPress site only removes obstacles; if nothing answers the reader's question, the settings alone change little. Google's SEO Starter Guide also advises reviewing previously published content and updating it, or deleting it when it is no longer relevant. Revisit your existing posts regularly and refresh anything that has aged.

A suggested maintenance habit

After every WordPress update, theme or plugin change and domain move, run a short check: the visibility box, the page source, robots.txt, the sitemap and a few sample addresses. It takes little time but can catch a noindex that would otherwise go unnoticed for months. If you keep the results in a notes file, the next comparison gets easier.

Frequently Asked Questions

What are the main WordPress SEO settings?

The core ones are the site title and addresses on the General screen, search engine visibility and homepage layout on the Reading screen, the URL structure on the Permalinks screen, and comment and link moderation on the Discussion screen. On top of those come the title, description, canonical, robots and sitemap output generated by your theme and plugins.

When should I tick the discourage search engines box?

Only on a site that is not ready to be public, such as one still in development. According to WordPress's documentation, the box adds a robots meta tag with noindex and disables sitemaps, but it does not block access. Once the site launches, verify that the box is unticked.

Which permalink structure should I choose?

A short, readable structure with hyphen-separated words suits most sites, and the post name option serves that purpose. Google says keywords in the domain or path have little ranking effect, so choose for readability and maintainability rather than for a ranking advantage.

Is it safe to change permalinks on a live site?

It is risky. Old addresses may not redirect automatically. Map old and new addresses, set permanent redirects and verify with a sample. If the change is not necessary, leaving the structure alone is safer.

Does WordPress have its own sitemap?

Yes. Since WordPress 5.5, core serves a sitemap index at wp-sitemap.xml. Your theme or a plugin may produce another one, so decide which is authoritative and submit only that one to Search Console.

Can noindex and robots.txt be used on the same page?

Not usefully. If robots.txt blocks the page, Google cannot see the noindex rule. To keep a page out of the index, allow crawling and add noindex.

Conclusion and Next Step

WordPress SEO settings boil down to five small decisions: define the site's name and address correctly, keep the visibility box unticked, choose a readable and lasting URL structure, keep sitemap, canonical and noindex signals consistent with each other, and verify every change in the page source. None of them carries a ranking guarantee, but each helps good content get found without being blocked.

My suggested next step is to run the checklist table above on your own site from top to bottom, write down every problem you find and then turn to content. If you need ready-to-publish articles, you can browse the content writing listings on Akua Adforce. Each listing's scope and terms are written on the related product and policy pages, and Akua does not promise that any article will deliver rankings, traffic or indexing. If content you commission includes a paid or sponsored placement, remember that Google describes marking such links with sponsored or nofollow.