WordPress Web Design and SEO: 10 Decisions to Make Before Launch

WordPress web design and SEO meet at a handful of decisions that are taken early in a build, often by someone who isn’t thinking about search at all. A designer picks a theme, a developer sets the permalinks, someone decides that the services page will be a slider with tabs. Each choice takes minutes before launch. Undoing it afterwards can take weeks, redirects and a dip in traffic.

I have worked in SEO and digital marketing for more than 16 years, and a large share of the WordPress rescue work I do traces back to these early calls. This article lists the 10 I want settled before a new site goes live, with what each one costs to get right now and what it costs to fix later.

If you want the wider case for bringing an SEO into the project at all, I have covered it in why WordPress and SEO services work better together, including the launch-day mistakes (the visibility setting, a staging robots.txt, a missing redirect map). Here I stay with the design and build decisions that come before that day.

The 10 WordPress web design and SEO decisions at a glance

Decisions 1 and 2: the URLs you will live with

1. Domain and canonical host

Decide the final domain, that the site runs on HTTPS, and whether the address is www or not. Then make every other version (HTTP, the other host, trailing slash variants) redirect to that one. It sounds trivial, but I still find new sites where two hosts both answer with a normal page, and where internal links, the sitemap and the canonical tags disagree about which one is real. Fix it on staging and test it on launch day.

2. Permalink structure

A fresh WordPress install uses the plain format. WordPress’s own permalinks documentation describes it as example.com/?p=N, “not user-friendly and also not optimized for search engines”, and lists the alternatives: day and name, month and name, numeric, post name and a custom structure. The same page says these URLs “are permanent and should never be changed”.

For most business sites I recommend post name, or a short custom structure if the blog needs a prefix. Dates in URLs make evergreen content look old and make a later restructure harder. Whatever you choose, choose it before the first post is published.

Decisions 3 and 4: structure before style

3. Page hierarchy and menus

Write the site structure as a list before anyone opens a design tool: the main service or product pages, the pages under each, and which pages the top menu, footer and breadcrumbs link to. Every important page should be reachable through normal links within a few clicks of the home page, and each page should have one clear job, so two pages don’t compete for the same search.

This is the work I do in a website structure review, and on a new build it costs a fraction of what it costs to restructure a live site. Decide categories for the blog at the same time. A handful of categories that match real topics beats dozens of tags that each create a thin archive page (I cover those archives in the WordPress technical fixes list).

4. Languages and countries

If the business will ever serve more than one language or country, decide the URL pattern now. Google’s guide to managing multi-regional sites compares the options. Country domains give “clear geotargeting” but are expensive and can “only target a single country”. Subdomains are “easy to set up” and allow different server locations. Subdirectories are easy to set up with “low maintenance (same host)”. URL parameters are “not recommended”.

In WordPress this choice also decides which multilingual plugin or multisite setup you use, so it is a build decision, not an SEO afterthought. If there is no second language on the roadmap, write that down too, so nobody installs a translation plugin “just in case”.

Decision 5: theme and page builder

The theme and builder decide how much code every page carries and how cleanly the content is marked up. I don’t ask for a particular brand. I ask the developer to show me a test page built with it, then I look at three things: whether headings are real heading elements, whether the main content is in the HTML the server sends, and how heavy the page is on a mobile connection.

Switching builders after launch usually means rebuilding every page, so this is the most expensive decision to reverse on the whole list. If the designer wants a premium theme with many bundled features, ask which ones the site will use and whether the rest can be switched off.

Decisions 6 and 7: templates and what Google can see

6. Title and heading templates

Each template (page, post, product, category) needs a sensible default title pattern and one visible main heading that matches the topic. In WordPress the most common faults I find are a logo or site name wrapped in the main heading on every page, and section labels styled as headings for looks. Set the pattern per template now. Afterwards it means editing pages one at a time.

7. Content in the HTML and crawlable links

Designers like tabs, accordions, sliders and “load more” buttons. They are fine as long as the text is in the page and the links are real links. Google’s guide to crawlable links says that “Generally, Google can only crawl your link if it’s an <a> HTML element” with an href attribute. Links inserted with JavaScript are crawlable too, as long as they use standard <a href> markup. Patterns such as a span with an href, or an onclick handler pointing to a URL, are listed as not recommended.

A menu that looks perfect but isn’t built from real links is a dead end for a crawler.

The same page says good anchor text is “descriptive, reasonably concise, and relevant”, and that for an image used as a link Google uses the image’s alt attribute as anchor text. So “Read more” buttons on every card and icon-only menus without alt text both waste internal links.

Decision 8: mobile content parity

Google’s mobile-first indexing best practices say that “Google uses the mobile version of a site’s content, crawled with the smartphone agent, for indexing and ranking.” It asks you to “make sure that your mobile site contains the same content as your desktop site”, to use the same headings, to keep the same structured data, and not to “lazy-load primary content upon user interaction”. It also says Google recommends responsive web design “because it’s the easiest design pattern to implement and maintain”.

In WordPress builds the problem is rarely a separate mobile site. It is the page builder’s “hide on mobile” switch: a block of text, a comparison table or a set of links shown on desktop and hidden on phones to tidy the layout. If it matters for search, it has to be on the mobile version.

Decision 9: images

Agree the image rules before the content team uploads hundreds of files. Google’s image SEO best practices give the essentials:

• Alt text is “the most important attribute” for image metadata. Write it to describe the image, without stuffing keywords.
• File names should be short and descriptive (its example contrasts my-new-black-kitten.jpg with IMG00023.JPG).
• Google finds images through the src of <img> elements, and “Google doesn’t index CSS images”. If a hero image matters, it should not be only a CSS background.
• With srcset or picture, always give a fallback URL in src.
• Supported formats include JPEG, PNG, WebP, SVG and AVIF.
• Place images near relevant text.

Decision 10: measurement from day one

Set up Search Console for the final domain, and analytics with any consent settings your country requires, before launch day. Record a baseline of the pages and keywords that matter on the old site, if there is one. Without it, nobody can say whether the new site helped or hurt. If URLs are changing, follow tracking rankings after a website migration for what to check in the weeks after.

How I work on new WordPress builds

I join WordPress projects as an hourly consultant, ideally at the sitemap stage. I review the structure and the 10 decisions with the designer and developer, check a staging build before launch, and do a short WordPress SEO audit after it goes live. If the site has already launched, the same list works as a repair plan: I rank the decisions by how much they are costing you and fix the cheapest high-impact ones first. You can read more about how I approach WordPress SEO consulting.

FAQ

How do I find the top WordPress website design agencies for SEO?

Ask each agency to walk you through these 10 decisions for your project. A strong one will have opinions on permalinks, structure, mobile content and image rules, and will show you a staging site before launch. A portfolio of attractive designs tells you about design, not about search.

Is an affordable WordPress web design SEO company good enough?

It can be, if the 10 decisions are written into the brief and checked. Cheap builds usually go wrong on structure, hidden mobile content and page builder weight, not on design. Paying an SEO for a few hours at the planning and staging stages often costs less than repairing a launched site.

Can I change my WordPress permalinks after launch?

You can, but every affected URL then needs a redirect from the old address, and internal links and the sitemap should be updated. WordPress’s documentation says permalinks should never be changed, which is why the choice belongs before launch.

Do I need a separate mobile design for SEO?

No. Google recommends responsive design as the easiest pattern to implement and maintain. What matters is that the mobile version carries the same content, headings, structured data and metadata as desktop.