WordPress SEO: Essential Settings Before Launch

WordPress SEO begins with making sure the platform is not hiding your site from Google. A few wrong settings, such as a forgotten checkbox, an unsuitable URL format or an archive indexed by accident, can cost months of visibility, and fixing them after launch is more expensive than checking them before. This guide walks through the essential settings in the order you should verify them, with the exact place in the dashboard and the reason for each.

What are essential WordPress SEO settings?

Essential SEO settings are the options that decide whether search engines can reach, understand and index your pages correctly. They are not tricks. They are basic conditions. Without them, good content never gets seen.

WordPress is flexible, and that is exactly why it leaves many choices to you. A default install produces numeric URLs, sample pages, date and tag archives and one checkbox that can block everything. A site built carefully from scratch avoids these traps at the start, as in a project to create an SEO-optimized site. If your site already exists, use the list below as a pre-flight check.

Order matters. First you make sure Google is allowed in, then that your addresses are stable, then that each page states its role clearly.

1. Check that search engines are allowed to index you

The first and most important check is in Settings > Reading, at the option "Discourage search engines from indexing this site." On a test or work-in-progress site the checkbox is useful. On a launched site it is the most expensive mistake available.

How it works: when the box is checked, current WordPress versions add a noindex robots meta tag to your pages (and turn off the built-in XML sitemap). Versions before 5.3 also wrote a Disallow: / rule into the virtual robots.txt. WordPress itself notes next to the option that it is up to search engines to honor the request. Google generally honors the noindex directive, so the practical effect is that your pages drop out of results over time.

Verify it three ways:

1. Open Settings > Reading and confirm the box is unchecked.
2. Open any page, press Ctrl+U to view the source and search for "robots". You should not find a noindex where you do not want one.
3. Open yoursite.com/robots.txt and confirm there is no Disallow: / for all crawlers. WordPress itself no longer writes this rule, but a plugin, a server setting or a leftover file from the test version might.

If you use WP-CLI, you can check the state quickly:

wp option get blog_public

A value of 1 means the site is visible to search engines, and 0 means indexing is discouraged.

One detail to watch: if robots.txt blocks a page, Google cannot read the noindex directive on it. To remove a page from the index, do not block it in robots.txt as well. You can build a correct file with the robots.txt generator.

2. Choose the permalink structure before you publish

Permalinks are the addresses of your pages. You set them in Settings > Permalinks. The old default, ?p=123, tells neither the user nor the search engine anything. The simple recommendation for most sites is "Post name," which gives /post-name/.

Why it matters: a descriptive address helps users understand the page, is easier to share and, according to Google's URL structure documentation, simple readable addresses are preferred. Avoid dates in the address unless you run a news site, because they make updating content awkward.

The golden rule is to lock the structure before launch. If you change it after pages are indexed, every old address must 301-redirect to the new one. See our guide to 301 and 302 redirects for how to do that correctly.

Check two more things: the category base (you can remove "category" from the address only if you understand the effects) and that page titles produce short slugs, without odd characters or filler words. If your site publishes in Romanian, the diacritics and slug fixer helps you avoid slug mistakes.

3. Fix the canonical version of your address: HTTPS and www

A site reachable in four variants (http://, https://, with and without www) looks to search engines like several addresses for the same content. Pick one and redirect the others to it.

In Settings > General, the "WordPress Address" and "Site Address" fields should contain your chosen version, with https://. Then:

• Install the SSL certificate at the hosting level (many hosts offer a free automatic one).
• Redirect HTTP to HTTPS, preferably at the server level.
• Choose between www and non-www, and be consistent in all internal links.

The check is simple: open each variant in a browser and confirm they all lead, in a single hop, to the same final address. If you see redirect chains, simplify them. For other duplicate-content cases, see our explanation of canonical tags.

4. Configure the SEO plugin: one only, with clear settings

WordPress ships without fields for each page's SEO title and meta description. An SEO plugin adds them. Several well-known options exist, such as Yoast SEO, Rank Math, All in One SEO and SEOPress; choosing among them is a matter of preference, not a decisive difference. What matters is using only one. Two plugins generating titles, canonicals or sitemaps in parallel produce duplicates and conflicts.

What you configure first, whatever the plugin:

1. Site type (person, organization) and name, so correct structured data is generated.
2. Title templates, for example %%title%% | Site Name, keeping an eye on displayed length. How to write them well is covered in the guide to title tags and meta descriptions.
3. Indexing rules by content type and taxonomy (see section 6).
4. The XML sitemap (see section 5).
5. Breadcrumbs and structured data, if your theme supports them, then validate them with Google's tools. For markup examples, see the guide to schema.org in JSON-LD.
6. Search Console connection, by verifying the property.

Do not stop at the plugin's green lights. They check length and keyword presence in a formal way, not text quality or search intent.

5. The XML sitemap: let one generator build it

Since version 5.5, WordPress generates a sitemap on its own at /wp-sitemap.xml (it is switched off while the discourage box is checked). Most SEO plugins create their own sitemap and turn off the core one. What matters is that exactly one sitemap is active, listing only indexable URLs that return a 200 response.

Checks:

1. Open the sitemap address and look for pages that are noindex, redirected or 404. There should be none.
2. Confirm the sitemap address appears in robots.txt (Sitemap: https://example.com/sitemap_index.xml).
3. Submit it in Search Console under Sitemaps.

You will find details on what to include and how to maintain it in the complete XML sitemap guide.

6. Decide on archives: tags, authors, dates, attachments

WordPress automatically creates archive pages, and many have little search value. They can dilute the index and create duplicate content.

Note: since WordPress 6.4, new installs redirect attachment pages to the file by default, but sites that were upgraded from older versions keep their attachment pages unless someone changes the setting. Check your SEO plugin for the attachment redirect option.

The decision rule: index an archive only if a person would have a reason to land there from search. If not, noindex, follow is a safe choice.

7. Clean up default content and comment settings

A fresh install comes with a "Hello world!" post, a "Sample Page" and an "Uncategorized" category. If they stay public, they stay in the index as pages with no value. Delete them or turn them into real content. Rename the default category.

For comments (Settings > Discussion), decide whether you want them. Unmoderated comments bring spam and unwanted links. WordPress normally adds rel="nofollow ugc" to comment links, but you still have to moderate. If you do not use comments, turn them off for new posts.

Also under housekeeping: set the site title and tagline in Settings > General, set the correct site language (it affects the lang attribute) and delete test users and pages.

8. Images, speed and mobile: what to set from day one

Speed is not solved by a single checkbox, but a few early choices help a lot. Pick a lightweight theme that does not load dozens of libraries on every page. Use fast hosting and a caching system. Upload images that are already resized, in a modern format, and fill in alt text.

For details, see the guide to image SEO and the explanation of Core Web Vitals. Test your homepage and one article with the site speed test, on mobile, not only on desktop.

9. The final pre-launch checklist

Work through the list in order, with the site on its final address.

1. The "Discourage search engines" box is unchecked.
2. robots.txt contains no Disallow: / and points to the sitemap.
3. Permalinks are set to "Post name."
4. All address variants lead to one HTTPS version.
5. One SEO plugin, with titles and meta descriptions filled in for key pages.
6. The sitemap lists only indexable pages.
7. Thin archives are noindex.
8. Default content is deleted.
9. Each page has a single H1 and ordered headings; see heading structure H1–H6.
10. The property is verified in Search Console and the sitemap is submitted.

After launch comes monitoring. For the first months, you will find a concrete plan in SEO for a new website: the first 90 days.

Common WordPress SEO mistakes

• Launching with the discourage box checked. This happens most often when a site moves from staging to production. The check in section 1 must be repeated after every move.
• Changing permalinks after launch, with no redirects.
• Installing two SEO plugins, or a plugin plus a theme that each generate their own meta tags.
• Indexing everything: tags, dates, attachments, internal search results.
• Trusting the plugin's traffic light without reading titles and descriptions the way a user sees them. You can preview them with the SERP simulator.
• Ignoring mobile and speed, convinced that "SEO is done by a plugin."

When these settings are not enough or do not apply

The list is a starting point, not a strategy. Correct settings do not produce rankings without useful content, a site structure built around what customers search for, and authority.

There are also cases where the details differ. A WooCommerce store brings filters, product variations and cart pages that need their own rules. A multilingual site needs hreflang. On a multisite network, settings apply per subsite. If you use a visual page builder, heading structure and speed need separate checks. Dashboard labels can vary slightly by WordPress version and interface language, so confirm each option in your own install.

Conclusion and next steps

A healthy WordPress SEO foundation comes down to a few decisions made on time: open visibility, stable addresses, one configured plugin, archives under control and a clean sitemap. Work through the list in section 9, then open Search Console and watch how the site gets indexed over the first weeks.

If you want all of this ready from the start, our site creation service builds it into the project. And to learn how to read the data after launch, continue with the Google Search Console beginner's guide.