Website Design for SEO: How to Build a Site Google Can Actually Rank
The structural decisions that settle whether Google can rank a page - made in the right order, by the person who has to live with them.
Website design for SEO means settling a site’s structure before anyone signs off on how it looks. Page hierarchy, URLs, templates, heading order, what loads first, what gets marked up. Handled in that order, design and SEO are the same job. Handled backwards, you pay for the site twice.
I have been working in search since 1990, and I build the sites I optimize. That means every decision on this page is one I have had to live with - including the ones I got wrong early and paid to undo. This is the order I work in and the reasoning behind it.
Updated September 19, 2026.
Design is not decoration. It is what Google reads.
Google does not see a page the way a client sees a mockup. It sees text, headings, links, markup and a load order. Every one of those is decided by design, not by writing. That is why a site can have good copy and still go nowhere.
Four design decisions carry most of the weight.
Hierarchy
Which pages exist, what each one is called, and what links to what. This becomes your URLs, your menu and your internal linking all at once. Get it wrong and every later fix is a redirect.
Templates
Each page type gets one repeatable pattern: heading order, image slot, FAQ block, calls to action. Whatever the template emits, it emits on every page. So does whatever it gets wrong.
Performance budget
Speed is a design constraint, not a plugin. A slider, a video header and five webfonts are budget decisions made before a line of code is written.
Markup
One H1, sensible H2s, and structured data emitted once by the template rather than bolted on by three plugins that disagree with each other.
Why this is written the way it is
I started in search in 1990. I built and sold Lotus411.com and later MSD2D.com, started Temecula SEO in 2007, and moved the practice to Tucson in 2022. I retired once and came back to work with a small number of local businesses instead of running an agency.
I am not describing a process I supervise. I write the copy, build the templates, hand-check the markup and answer the phone when something breaks. Two client sites are in front of me most weeks, and everything below is what I actually do on them.
The order I build in
The order matters more than any single item on the list. Steps taken out of sequence are what turn a cheap decision into an expensive one.
- Inventory the pages first. Every page, its URL and its parent, written down before anything is built. This is the site’s hierarchy, and it is the one thing that is genuinely painful to change later.
- Give each page one keyword and one intent. One page owns one query lane. Two pages chasing the same phrase split the signals and neither wins. Decide whether the visitor wants to learn, to compare or to hire, and build for that answer only.
- Outline the copy before the layout. Real headings first. A layout designed around placeholder text always ends up squeezing the content that pays the bills.
- Design the phone version first. Google indexes the mobile version. If something is cut on mobile to keep it tidy, assume it does not exist.
- Decide the hero and the image rules up front. One main image per page, in the HTML, sized, compressed and prioritized. That single decision is usually the difference between passing and failing on load speed.
- Build the internal links on purpose. Every page links up to its parent, across to its siblings and out to the page you want people to act on. Anchor text that says what is on the other end.
- Put the markup in the template. Structured data written once, referencing one set of business entities, so twenty pages cannot describe the same business twenty different ways.
- Launch with Search Console and a full crawl. Sitemap submitted, every internal link checked, every redirect checked. The first week after launch is when the cheap fixes are still cheap.
Steps three and six are the ones people skip, and they are the two I most often get hired to unpick. If you want the writing handled as part of the build, that is covered on SEO content writing.
The technical floor a design has to clear
This is the short version. There is a longer treatment on technical SEO, but a designer needs these four numbers and nothing else.
Core Web Vitals. Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, Cumulative Layout Shift under 0.1. Google judges these on real Chrome visits at the 75th percentile over a rolling 28-day window, not on a test run from your own laptop. INP replaced First Input Delay in March 2024, so any brief still listing FID is out of date.
Mobile-first indexing. The phone version is the version that gets indexed. Content hidden from mobile is content removed from your site as far as ranking is concerned.
HTTPS everywhere. Certificate installed before launch, every HTTP address redirected once to its HTTPS equivalent, canonicals and sitemap pointing at the final address only.
Rendered, not drawn. If the service description, the prices or the FAQ only appear after a script runs, treat them as unindexed until Search Console proves otherwise.
Designing for local search
For a business serving a city, a handful of design decisions carry more weight than everything else combined. They are all template decisions, which is why they belong in the design phase.
Put the business name, address and phone in the footer template as real text, formatted exactly as it appears on the Google Business Profile. Emit LocalBusiness structured data once, sitewide, rather than letting three plugins each publish their own version. Put the city in the title tag of the pages that serve a city. Build a genuine page for each area you actually serve, with content that could only have been written about that area - not a template with the city name swapped in. Embed the map on the contact page.
None of that is difficult. It is just easier to do while the templates are being built than to retrofit across forty pages. If you want it done for a Tucson business, that is what I do.
What a small business site actually needs
Everything above is about the structure underneath a site. This section is about the finished thing - what has to be on the page once the templates are built. It is the list I work down when a small business asks me to look at a site that is not producing calls.
Most of the sites I audit fail for boring reasons. The phone number is buried in an image. The page takes six seconds to open on a phone. The menu has fourteen items and none of them say what the company does.
None of that is exotic and all of it is fixable in an afternoon. Here are the eight things I check first, in the order I check them, and the reason each one matters.
1. It works on a phone, not just displays on one
Working means thumb-sized tap targets with space around them, body text at 16px or larger so iOS does not zoom your form fields, short paragraphs written for a narrow column, and nothing overflowing sideways. One set of responsive pages, never a separate m-dot site.
Google finished moving to mobile-only crawling on 5 July 2024. If a site will not load on a phone it cannot be indexed at all. A site that loads but looks dated on mobile is still indexed - it just converts badly. That difference matters if someone is trying to sell you an emergency rebuild.
2. It loads before people give up
Google's 2017 mobile benchmark put abandonment at 53% of visits past three seconds. It is an old study and still the best-sourced number in the field, which tells you how much speed advice online is invented.
The cause is nearly always one of four things, worth checking in this order: uncompressed images straight off a phone, cheap shared hosting that takes a second to think, thirty plugins where ten would do, and no page caching or CDN.
3. A stranger can navigate it
You know where everything is on your own site, which is exactly why you cannot judge the menu. The test is whether someone who has never heard of you can find your phone number, your main service and your service area in ten seconds.
Five to seven menu items, in the words customers use. "Drain Cleaning" and "Get a Quote", not "Solutions" and "Offerings". Phone number in the header as a real tel: link on every page, and the key links repeated in the footer.
4. There is one obvious next step
Most small business homepages I audit have either no clear call to action or six competing ones, which amounts to the same thing. Pick one primary action per page and start the button with a verb. "Get a Free Estimate" beats "Contact Us" because it says what you get.
Repeat it near the top, after each major section and in the footer. Secondary actions are fine as long as they are visually quieter, so the hierarchy stays obvious.
5. It is built so Google can read it
One clear topic per page, one H1, unique title tags and meta descriptions, clean URLs, descriptive alt text and internal links that connect related pages. Retrofitting any of that costs more than building it in.
For a local business, add the location layer: a real page for each city you genuinely serve, and name, address and phone written identically everywhere. Google is matching entities, not strings. If you would rather have someone look at your specific site, that is what an SEO audit is for.
6. It looks like the same company everywhere
Two or three colors used consistently, two fonts rather than five, a logo that is sharp instead of a stretched JPEG. The reasoning is uncomfortable but fair: if a business will not fix the blurry logo on its own homepage, why would a customer believe it will be fussy about their roof?
The figure everyone quotes - that 75% of people judge a company by its design - is a distortion. The actual Stanford Web Credibility research found 46.1% cited visual design. Still the single most-cited factor, and still enough to make the point.
7. It carries proof from real customers
You saying you are reliable is a claim. A customer saying you showed up on a Sunday is evidence. Put reviews where the decision happens - beside the call button, on the service pages - not quarantined on a testimonials page nobody visits, and use the detailed ones.
Always attribute. A first name, a last initial and a city beats an anonymous quote by a wide margin; an unsigned testimonial reads as invented. Put reviews on the page because they convert, not because you expect stars in Google. See the next section for why.
8. It is secure and maintained
HTTPS is table stakes - not for rankings, but because Chrome writes "Not Secure" next to your address while someone decides whether to type their phone number into your form. Most hosts include a free certificate and switching it on is one click.
The rest is unglamorous and non-negotiable: CMS and plugins updated, spam protection on forms, a published privacy policy, automated backups stored off the web server, and accessibility basics to WCAG. I have watched a business lose eleven years of content to a hosting failure with no backup.
If you can only do a few of these this month
Do them in this order. It is the sequence I work in on a real client site, because each step makes the next one measurable.
- Make the phone number a tappable link in the header of every page. Fastest change, quickest effect on calls.
- Compress the images. Usually the largest single speed gain available, and it costs nothing.
- Turn on HTTPS if it is not already on, and redirect the HTTP version once.
- Cut the main menu to five or seven plainly-named items.
- Write one primary call to action per page and repeat it down the page.
- Write unique titles and meta descriptions for every page. Duplicates are extremely common and easy to fix.
- Make your name, address and phone identical across the site, the Google Business Profile and the directories.
- Add three attributed customer reviews to the homepage and the top service pages.
What changed in 2026, and what most design guides still get wrong
A lot of website design advice still circulates from checklists written years ago. Four items on those checklists are now simply wrong, and you can date a proposal by whether it repeats them.
FAQ rich results are gone. As of May 7, 2026 they no longer appear in Google Search, and the reporting in Search Console is being retired behind them. Google had already restricted them to government and health sites in 2023; the 2026 change closes the door entirely. FAQPage remains a valid schema.org type and does no harm, so I still ship it - it labels questions and answers for anything reading the page. I no longer sell it as a way to get a bigger search result, because it is not one.
HowTo rich results are gone too, removed on desktop and mobile back in 2023 and the documentation withdrawn with them. Step-by-step markup is fine to keep; expecting a visual treatment from it is not.
Review stars from your own markup are not coming. Since 2019 Google has treated reviews about a business, published on that business’s own site, as self-serving and ineligible for the star review feature on LocalBusiness and Organization markup. That includes reviews pulled in by a third-party widget. Your stars in the map pack come from your Google Business Profile. No amount of schema on your homepage will add them to an organic listing.
There is no HTTPS penalty. Google announced HTTPS as a ranking signal in 2014 and described it as very lightweight, affecting under 1% of queries. Anyone selling you a certificate on the threat of a penalty is inventing one. Do it for the browser warning and your customers’ data, which are reasons enough.
Anyone quoting a website design package on the promise of FAQ snippets or schema-driven review stars is quoting from a stale checklist. Ask when they last read the documentation.
Where design quietly costs you rankings
These are the ones I find on almost every site I inherit. Each is a design decision, each was free to avoid, and each costs real money to unwind after launch.
| Design decision | What it costs you | How I build it instead |
|---|---|---|
| Hero image set as a CSS background, or lazy-loaded | Largest Contentful Paint misses 2.5s on mobile | Real img in the HTML, fetchpriority="high", width and height on the tag |
| Theme prints one H1 and the content adds another | Two competing topic statements on one page | One H1 per page, stated in the words people search |
| Theme and SEO plugin both emit structured data | Duplicate, contradicting entities for the same business | One source of truth sitewide, every page referencing it by @id |
| Headline or offer baked into a JPG | Invisible to crawlers, assistants and screen readers | Real text in the markup, image used for the picture only |
| Key content inside script-drawn tabs or accordions | May never be indexed | Ship the text in the HTML; let script only show and hide it |
| One title template repeated across every page | Pages compete with each other for the same query | One keyword lane per page, mapped before the build |
| Menu links pointing at an old or staging URL | Every internal click spends a redirect and leaks equity | Audit the nav after launch, not just the page bodies |
| Photos uploaded straight off the camera | Multi-megabyte pages, failed vitals on cellular | Resize to the display size, compress, serve WebP or AVIF |
| Fonts, banners and embeds loading with no reserved space | Cumulative Layout Shift over 0.1 | Set explicit dimensions so nothing jumps as it loads |
| New pages published with nothing linking to them | Orphans that Google may take months to find | Link every new page from its parent page before publishing |
Writing pages that both people and assistants can use
Assistants like ChatGPT and Google’s AI Mode fetch a page, reduce it to text and look for a direct answer near the question. That is not a different discipline from good writing. It is the same discipline, enforced more strictly.
State the answer in the first sentence, not the fourth paragraph. Give each page one subject so a machine deciding what the page is about does not have to choose. Write headings that say what is underneath them rather than being clever. Name things explicitly - the city, the business, the product - because a system extracting an answer cannot resolve “we” or “here”. Put the facts in the HTML rather than behind a script.
Do that and you have also written a page a hurried human can scan on a phone, which was the point before any of this existed.
What clients say
David built and developed the website for my business. His customer service and expertise are superior to anyone else I had previously used. How many web development guys had I been through that promise the moon, work hard for a short while, then become difficult to get a hold of later? I'll tell you: there were 9 in 7 years! Temecula SEO worked with us closely, is VERY knowledgeable and computer savvy! It's so nice to have a custom website built; and, actually see it rank well on-line! If you want an SEO guy you can count on, David with Temecula SEO is your man!
Leo Rich Severns Master TechnicianWe have worked with David for over a year now and he is great to work with. David has built us a great new website that we love and our Google ranking has improved significantly. David is a great guy and works day and night to help you. I highly recommend Temecula seo. Thank you David for your hard work.
Jason MoatIf you are looking for help with SEO, or anything related, David is your man! I talked to several other companies before talking to David, and I knew right away he was different. He is extremely professional, responsive, affordable, and effective. Most importantly, I trust that he is looking out for my best interest. He takes a very hands-on approach and always takes the time to listen to the changing needs of my professional business. His wealth of knowledge is invaluable. He had my business seeing results almost immediately. Thank you David for all your hard work! Best in the business!
Luke HendrixDavid is great to work with. He takes his job seriously, is a wealth of knowledge not only in SEO, but also business in general. If you are looking to for someone to handle SEO for you - you can stop looking now.
Russ ColburnQuestions about designing a site to rank
What is website design for SEO?
Website design for SEO is the practice of settling a site's structure - page hierarchy, URLs, templates, heading order, image handling and structured data - at design time instead of after launch. It puts search requirements in the design brief. Visual style is a separate question. A plain site with clean structure will out-rank a beautiful one that buries its content.
Does website design actually affect Google rankings?
Yes, indirectly and heavily. Google does not rank a site for being attractive. It ranks pages it can crawl, render, understand and load quickly for real people. Design decides all four: what the crawler finds, how the content is labeled, how fast the main image paints, and whether the phone version contains the same content as the desktop version.
Which comes first, the design or the content?
The content, or at least the outline. A layout designed around real headings and real copy fits the page. Copy poured into a layout built around placeholder text always gets cut, padded or pushed below the fold. I outline the page first, then design to what is actually there.
Does a better-looking website rank higher than a plain one?
Not on looks. Appearance reaches rankings only through behavior and performance: whether people stay, how fast the page paints, and whether the layout holds still while it loads. A heavy design with a slider, a video background and five webfonts usually loses to a plain fast page. Design well, but spend the performance budget first.
What does a small business website actually need to have?
Seven things, at minimum. A page that loads and works on a phone. A tappable phone number in the header of every page. One clear call to action. A page for each service you sell. Your name, address and phone written identically everywhere. HTTPS. And attributed customer reviews. Everything beyond that is an improvement rather than a requirement. Most small business sites that underperform are missing three or four items from that list, not something exotic.
How many pages should a small business website have?
A local service business usually needs one page per service it sells, one page per city it genuinely serves, plus a home page, an about page, a contact page and a privacy policy. For a typical trades or professional business that lands somewhere between eight and twenty-five pages. The rule is one page per thing a customer would search for separately. Do not build a page for a city you do not actually serve; those pages rarely rank and they damage trust when a customer works out you are ninety minutes away.
What should be in a design brief before the build starts?
A page inventory with the URL for every page, one target keyword and one search intent per page, who writes the copy, a performance budget such as Largest Contentful Paint under 2.5 seconds on a phone, the structured data each template has to emit, and who owns the site and the hosting after launch. That brief costs nothing at the start and thousands to retrofit.
Which SEO problems get expensive to fix after launch?
URL structure, page hierarchy and anything baked into a theme template. Changing URLs later means redirects, lost link equity and a re-crawl. Changing heading structure or schema output means touching every page built on that template. Titles, copy and images stay cheap to change. Structure does not.
How can I tell if my site's design is holding back its rankings?
Load the page on a phone on cellular data and watch how long the main image takes. View the source and count the H1 tags and the JSON-LD blocks. Click the main menu and see whether any link redirects before it lands. Then run the URL Inspection tool in Search Console and compare what Google renders with what you see on screen. Missing text means it is being drawn by script and may never be indexed.
Do ChatGPT and Google's AI Mode read a page the same way Google's crawler does?
Not identically. An assistant usually fetches the page, strips it to text and looks for a direct answer close to the question. That rewards the same structure Google rewards: one clear topic per page, honest headings, and the answer stated in the first sentence rather than the fourth paragraph. It punishes content that only exists after a script runs. Structured data helps because it labels the entities instead of leaving them to be guessed.
Is it still worth building FAQ sections into pages now that Google has dropped FAQ rich results?
Yes, for readers and for machine comprehension, not for the search appearance. Google retired FAQ rich results on May 7, 2026, and the HowTo rich result was removed back in 2023. FAQPage is still a valid schema.org type and causes no harm. Keep the FAQ if it answers questions buyers actually ask. Delete it if it only ever existed to chase a snippet that no longer appears.
If you want this built rather than explained
I build sites for a small number of local businesses, one at a time, and I do the work myself. There is a fixed monthly fee and no contract. See how a build works, read what it costs and what is included, or get in touch for a free consultation. If you already have a site and want to know what is holding it back, start with an SEO audit. Or call (520) 207-6000.
About the author
David Cragg has worked in search since 1990. He built and sold Lotus411.com and MSD2D.com, holds an economics degree from UCLA and an MBA from the University of Washington, founded Temecula SEO in 2007 and has run Tucson SEO from Tucson, Arizona since 2022. He writes, builds and maintains every client site himself.
On method: I draft with AI assistance and I say so. AI helps me research, structure and check my own work. It is not permitted to supply facts about a client's business, invent a statistic, or publish anything I have not read. Every number on this page is traceable to the source linked beside it - which is why several widely-repeated statistics have been corrected rather than repeated. My full position is on the content creation page.
