The short answer: web design and SEO are two halves of one job. Design decides what visitors see and do once they land on your site. SEO decides whether they find it in the first place. Google doesn't rank a site for looking good, but the decisions your designer makes (how pages load, how they work on a phone, how they're linked together, whether the words are real text) shape what Google can read and measure. Get those decisions right while the site is being built, and SEO becomes upkeep instead of a rescue job.
Most guides on this topic list the same principles and stop. This one gives you the checklist we actually use: which design choices matter, how to test each one yourself in a few minutes, what to protect during a redesign, and who should handle the work after launch. If you want the full picture of SEO work beyond your website's design, start with our SEO services for small business guide.
How web design affects SEO (what Google actually says)
There's a lot of folklore here, so start with what Google has documented:
- Core Web Vitals are used in ranking. Google says "Core Web Vitals are used by our ranking systems," and that there is no single "page experience signal" (Google Search Central: page experience).
- The rest of page experience helps indirectly. In the same page, Google says other page experience aspects "don't directly help your website rank higher," but they make a site more satisfying to use, "which is generally aligned with what our ranking systems seek to reward."
- Google mostly judges pages one at a time. Its core ranking systems "generally evaluate content on a page-specific basis," with "some site-wide assessments." A slow homepage doesn't doom your service pages, and a fast homepage doesn't save them.
- Google ranks the mobile version. Google uses the mobile version of a site's content for indexing and ranking, and recommends responsive design (Google: mobile-first indexing).
So design matters for SEO in two ways. Directly, through speed, stability and what Google can crawl. Indirectly, through whether visitors find what they came for and turn into calls, bookings or sales.
Web design vs web development vs SEO: who controls what
When a site underperforms in search, the fix often sits with a different person than the one you'd call. Here's how the work splits:
| Discipline | What it controls | How it shows up in search | Typical mistake |
|---|---|---|---|
| Web design | Layout, navigation, typography, images, calls to action, mobile layout | Layout shift, mobile usability, whether visitors stay and convert | Putting key text inside images or sliders |
| Web development | Code, platform, hosting, plugins, rendering, redirects | Load speed, crawlability, Core Web Vitals, broken pages | Heavy themes, scripts and plugins on every page |
| SEO | Keywords, page titles, headings, content, internal links, schema, listings | Which searches you appear for, and where you rank | Starting after the site is already built |
On a small business site, one person or tool often does all three. That's fine, as long as someone owns each column.
The SEO-friendly web design checklist
Ten design decisions, what good looks like, and how to check each one yourself.
1. Put your words in the HTML, not in images or scripts
If your main text only appears after JavaScript runs, or lives inside an image, banner or slider, search engines have to work harder to read it, and some can't. Google renders JavaScript in a later step and can take longer to do it, and says "server-side or pre-rendering is still a great idea because it makes your website faster for users and crawlers, and not all bots can run JavaScript" (Google: JavaScript SEO basics).
How to check: open a key page, right-click and choose "View page source" (not "Inspect"). Search for your headline and a sentence from the page. If they aren't there, the page depends on JavaScript to show its content.
We hit this on one of our own sites. A small safety-training software company's topic pages were mostly empty in the raw HTML. Making those pages readable without JavaScript was one of several fixes that week, alongside switching off a thin AI auto-blog and retitling pages close to page one. Google clicks went from 5 to 33 a week (the full case study). We can't credit the rendering fix alone, but it was the foundation the rest depended on.
2. Design mobile-first, with the same content on every screen
Responsive design (one URL, one set of HTML, a layout that adapts) is what Google recommends because it's the easiest to get right. The trap is hiding content on phones to save space. Google says having the same content on desktop and mobile "ensures that the two versions can rank for the same keywords." If a section, FAQ or set of links is missing from the mobile layout, assume Google doesn't see it.
Design for thumbs, too: tap-to-call phone numbers, buttons big enough to tap, text readable without zooming, and the main call to action visible without scrolling.
How to check: open your key pages on your own phone, not just a resized desktop browser. Compare them section by section with the desktop version.
3. Hit Core Web Vitals targets
Core Web Vitals are three measurements of real visitors' experience. Google's recommended targets (web.dev: Web Vitals):
| Metric | What it measures | Good | Design choices that usually hurt it |
|---|---|---|---|
| LCP (Largest Contentful Paint) | How fast the main content loads | Within 2.5 seconds | Huge hero images, sliders, video backgrounds, slow hosting |
| INP (Interaction to Next Paint) | How quickly the page responds to taps and clicks | 200 milliseconds or less | Heavy scripts, chat widgets, too many plugins and trackers |
| CLS (Cumulative Layout Shift) | Whether the layout jumps while loading | 0.1 or less | Images without set sizes, late-loading banners, pop-ups, web fonts swapping in |
Google says the good threshold to aim for is the 75th percentile of page loads, measured separately for mobile and desktop. In plain terms: most of your real visitors, not just you on fast office Wi-Fi.
Design fixes that usually help: resize and compress images before upload, use a static hero image instead of a slider, set width and height on images and embeds, lazy-load images below the fold (but never the main hero image), limit custom fonts, and load chat widgets and pop-ups after the page is usable.
How to check: run key pages through Google's PageSpeed Insights, and check the Core Web Vitals report in Google Search Console once your site has enough traffic for real-user data.
4. Keep site structure shallow and logical
Your navigation is also the map search engines use to find pages. Design it so:
- Every important page (each service, each location) is linked from the menu or a hub page, a few clicks from the homepage at most.
- No page is an orphan. If nothing links to a page, Google may never find it.
- Related pages link to each other in the body text, not just the menu.
- Breadcrumbs show where a page sits ("Home › Services › Drain Cleaning") on deeper sites.
Use real links. Google says it "can only crawl your link if it's an <a> HTML element" with an href attribute (Google: link best practices). Menus or buttons that navigate only through JavaScript click handlers can hide whole sections of a site. Use descriptive anchor text: "drain cleaning in Springfield," not "click here."
5. Use simple, descriptive URLs
Google recommends descriptive URLs with words people understand, and hyphens rather than underscores between words (Google: URL structure). /services/drain-cleaning beats /page?id=482. URLs are case sensitive, so pick lowercase and stick to it. Decide your URL pattern before launch, because changing it later means redirects (see the redesign section below).
6. Build page templates that get the on-page basics right
Templates set the defaults for every page on the site, so a mistake in one template repeats everywhere. Each template should allow:
- A unique, editable title tag and meta description per page (no "Home | Home" or blank defaults).
- Exactly one H1, then H2s and H3s in order. Headings are structure, not font sizes.
- A self-referencing canonical tag on indexable pages.
- An editable FAQ block for service pages. Short, direct answers in text help with search and AI answers.
7. Treat images as content, not decoration
Google's image guidance (Google: image SEO best practices) comes down to:
- Use standard HTML image elements, not CSS backgrounds, for images that matter.
- Write descriptive alt text. Google says alt text is "the most important attribute" for image metadata. Describe what's in the photo: "technician replacing a water heater," not "image1."
- Use short, descriptive file names (
water-heater-replacement.jpg). - Serve responsive sizes and a supported format, and compress for speed.
- Use real photos of your work, team and premises where you can. They do more for trust than stock images.
8. Add structured data that matches the page
Structured data (schema markup) tells search engines exactly what a page is about: your business, your address and hours, your breadcrumbs, your FAQs. Two rules from Google: the markup must describe content that's visible on the page, and Google "does not guarantee" that rich results will show (Google: LocalBusiness structured data).
A basic block for a local business's contact page looks like this. Replace every value, and keep it identical to what the page and your Google Business Profile show:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Example Plumbing Co.",
"url": "https://www.example.com/",
"telephone": "+1-555-555-0100",
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Main St",
"addressLocality": "Springfield",
"addressRegion": "IL",
"postalCode": "62701",
"addressCountry": "US"
},
"openingHoursSpecification": [{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "08:00",
"closes": "17:00"
}]
}
</script>Use a more specific type if one fits (Plumber, Dentist, AutoRepair). Test every template in Google's Rich Results Test before launch.
9. Keep it secure and free of intrusive pop-ups
Serve every page over HTTPS. Google's page experience self-assessment asks whether your pages "avoid using intrusive interstitials" and whether visitors can easily tell the main content from everything else. A full-screen pop-up the moment someone lands on a phone fails both.
10. Design for accessibility
Accessible design overlaps heavily with SEO: real text instead of text in images, alt text, a logical heading order, descriptive link text, and enough color contrast to read. It also opens your site to more customers.
Redesigning? How to keep the rankings you already have
A redesign is where most small businesses lose search traffic, because search engines rank pages, not sites. Change a page's address without a redirect, and the history that page built up is left behind. Before you launch a new design:
- Save a baseline. Export the last 3 months of clicks, impressions and top pages from Google Search Console. Without a "before," you can't judge the "after."
- List every old URL. Crawl the current site or export the sitemap. Every URL needs a destination.
- Keep URLs that already rank. The safest redirect is the one you don't need.
- Map 301 redirects one to one. Each old page goes to its closest new equivalent, not everything to the homepage. Google recommends server-side permanent redirects, no chains, and keeping redirects "generally at least 1 year" (Google: site moves with URL changes).
- Carry over what works. Keep titles, headings and body text on pages that perform. Improve them after launch, one at a time, so you can see what helped.
- Test on staging, but block it from Google. Password-protect the staging site, then remove every noindex tag and robots.txt block when you go live.
- Submit the new sitemap in Search Console on launch day and check the Pages report daily for the first couple of weeks.
Pre-launch and post-launch checklist
| Check | What good looks like |
|---|---|
| Indexing | No leftover noindex tags; robots.txt allows public pages; staging password removed |
| Firewall and CDN | Bot-protection settings aren't blocking Googlebot or Bingbot |
| Rendering | Headline, body text and links appear in "View page source" on each template |
| Titles and descriptions | Unique on every page, no placeholders, one H1 per page |
| Canonicals | Self-referencing on indexable pages, pointing at the live HTTPS URL |
| Status codes | 200 for live pages, 404 for removed pages, single-hop 301s for moved pages |
| Sitemap | Only live, canonical URLs; submitted in Search Console |
| Mobile | Same content as desktop; tested on a real phone |
| Core Web Vitals | Key templates checked in PageSpeed Insights; images sized; no layout jumps |
| Structured data | Passes the Rich Results Test and matches the visible page |
| Tracking | Search Console verified; analytics and form tracking working |
| After launch | Search Console Pages report and clicks checked weekly against your baseline |
Web design and AI answers
People now ask ChatGPT, Google's AI Overviews and other assistants who to hire. The good news: there's no separate design spec for this. Google says there are "no additional requirements to appear in AI Overviews or AI Mode" (Google: AI features and your website). The same foundations apply: pages that load and render as real text, clear headings, and short, direct answers to the questions customers ask. One design-specific check: if your host or CDN has "bot protection" settings, make sure they aren't blocking the search crawlers you want. For what AI-focused SEO work should include, see our guide to AI SEO services.
Web design mistakes that quietly hurt SEO
- A homepage slider carrying your main headline and services as images.
- "Coming soon" or staging noindex tags left in place after launch.
- Service details hidden in tabs or accordions that don't exist on the mobile layout.
- One "Services" page listing everything instead of a page per main service.
- Navigation built only in JavaScript, with no real links.
- Pop-ups that cover the page as soon as a visitor arrives on a phone.
- A redesign that changes every URL with no redirect map.
- Uploading full-size photos straight from a camera or phone.
- Copy-pasted city pages with only the town name swapped. Google treats pages built that way as doorways; our local SEO for small business guide covers how to do area pages properly.
Should you hire a web designer who does SEO?
It depends on what you need right now:
- Building a new site or redesigning: hire a designer or developer who can show you, on sites they've built, that pages render as real HTML, pass Core Web Vitals and kept rankings through a redesign. Ask for their redirect plan before you sign.
- Your site is fine but nobody finds it: you probably don't need a redesign. You need ongoing SEO: titles, service pages, local listings, content and weekly checks. A new design won't fix that on its own.
- Both: have the designer build to the checklist above, and have whoever does your SEO review the templates and redirect map before launch.
Questions to ask any web designer: Who writes the page titles and meta descriptions? Will text be real HTML? How will you handle redirects from our current URLs? Can we edit titles, headings and FAQs ourselves after launch? Who owns the domain, hosting and analytics accounts? (The answer to the last one should be you.)
What an AI SEO employee does after the site launches
A well-designed site is the starting line. Hours change, pages go stale, plugins update, and Google reports new issues. This is repeatable work that an AI employee handles well, with a person approving changes.
Here's how Sam, our AI SEO employee, runs it:
| When | What gets done | What you see |
|---|---|---|
| Week 1 | Audit: indexing, rendering, sitemap, redirects, titles, H1s, Core Web Vitals flags, schema on key templates | A prioritized fix list for your approval |
| Weeks 2–4 | Fix approved titles, metas and headings; set up or correct schema; flag speed and layout issues for whoever manages your site | Each change logged with its URL |
| Every Monday | Compare Search Console clicks, impressions and rankings for agreed searches against the week before | A short weekly report |
| Every week | Check for new indexing errors, broken links and redirect problems; improve one service page with answer blocks and FAQs | Issues found and fixed, with dates |
| Monthly | Keyword board and briefs for new pages; recheck Business Profile and directory listings | A one-page plan for the month |
| Before any redesign | Baseline export, URL inventory, redirect map review, post-launch indexing checks | A redirect map and a launch-week report |
What Sam doesn't do: design or rebuild your website, run ads, buy links or guarantee rankings. He works on the SEO side of your existing site and flags design and code fixes for your web person. You approve page changes and business claims before they go live.
Who should handle SEO for your site
You can do every item on the checklist above yourself; most of it is careful and consistent upkeep. The hard part is keeping it up every week for years.
If it keeps slipping, Sam, our SEO/AEO Specialist, is part of Stewart Labs' digital staff: AI-powered, not a human employee, with a person on our team running your account. His scope covers technical SEO (indexing, sitemap, redirects and speed flags), on-page titles, metas and H1s, local and service pages, Google Business Profile hygiene, AEO answer blocks and FAQs, directory listings, citations and backlink outreach, and a weekly rankings and clicks report. The role is $599 a month, with free setup. See Sam's digital staff role.
If your new site needs service pages and blog posts written, Courtney, our content writer, turns your real work into helpful pages from Sam's briefs, at the same $599 a month per role, free setup. See Courtney's digital staff role, or meet all our digital staff.
Get a free growth audit
We'll check whether Google can read your pages, how your key pages score on Core Web Vitals, and which titles and pages to fix first. Get a free growth audit.
FAQ
Does web design affect SEO?
Yes. Google doesn't rank a site for looking good, but design and build choices control things Google does use: Core Web Vitals, how the mobile version looks and what it contains, whether text and links can be crawled, and how pages link together. Design also affects whether visitors find what they need once they arrive.
Should I do web design or SEO first?
Plan them together, before the site is built. URL structure, page templates, navigation and how pages render are expensive to change once a site is live. If your site already exists and works on phones, you usually don't need a redesign to start SEO.
Can a website redesign hurt my rankings?
It can, if URLs, titles or content change without a plan. Save a Search Console baseline, keep URLs that rank, map one-to-one 301 redirects for any that change, and keep those redirects for at least a year, as Google recommends.
What are good Core Web Vitals scores?
Google's targets are a Largest Contentful Paint within 2.5 seconds, an Interaction to Next Paint of 200 milliseconds or less, and a Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of real page loads on mobile and desktop.
Do I need a web designer who does SEO?
For a new build or redesign, choose a designer who can show that their sites render as real HTML, pass Core Web Vitals and keep rankings through redesigns. For ongoing visibility, you need regular SEO work, which a designer may or may not offer. Ask who writes titles, handles redirects and reports on search results after launch.
Sources (fetched Nov 20, 2026): Google Search Central documentation on page experience, mobile-first indexing, JavaScript SEO basics, link best practices, URL structure, image SEO, LocalBusiness structured data, site moves with URL changes, and AI features; web.dev Web Vitals. Case study numbers are from a site we operate. Search volume from our own keyword research.