What this covers
-
1. the Heading Hierarchy Is an Outline, Not a Font-Size Menu
-
2. Content Behind a Click Is Content Discounted
-
3. Above the Fold Decides Whether the Rest Gets Read
-
4. Images Need to Be Described, Not Just Compressed
-
5. Speed Is a Real Input, and the Fix Is Usually Images
-
6. the Redesign Redirect Map, Which Is Where the Real Money Goes
-
The Newest One: Can a Machine Read the Page at All
-
Design Decisions With Search Consequences
-
What to Check on a Phone Before Launch
-
Keeping the Two Conversations Together
-
Where This Leaves the Design Brief
There is an old and unhelpful framing where design and search optimization are opposing forces, with designers wanting something beautiful and search people wanting something ugly and stuffed with keywords. That has not been true for a long time, and it obscures something more useful: a handful of design decisions carry direct search consequences, and most of them are invisible in a mockup.
Here are six, with the mechanism attached to each.
1. the Heading Hierarchy Is an Outline, Not a Font-Size Menu
Headings are the closest thing a web page has to a table of contents. A machine reads them in order and builds a model of what the page is about and how its parts relate.
The failure mode is using a heading level because of how big the text looks. A designer wants a small subhead so reaches for an H4, or wants a big pull quote so wraps it in an H2. The visual result is correct. The structural result is an outline that says the page’s second-most-important idea is a decorative quote.
Use the level that reflects the actual hierarchy and style it to look however you want. One H1 per page that states the subject. H2s for genuine sections. H3s for subsections beneath them. Nothing skipped.
This matters more now than it did, because the same structure is what an AI system uses to decide which part of your page answers a question well enough to quote.
2. Content Behind a Click Is Content Discounted
Accordions, tabs and read-more toggles are tidy. They are also a way of telling a machine that the hidden material is secondary.
Content that requires an interaction to reveal has historically been weighted lower than content visible on load, and the logic is straightforward: a search engine cannot click, and content most visitors will never see is, by reasonable inference, less important.
This creates a genuine tension with mobile layout, where collapsing long sections is good for the reader. The workable compromise is to keep the substance visible and use collapsing for genuinely supplementary material, rather than hiding your main service description inside a tab labeled “Details.”
3. Above the Fold Decides Whether the Rest Gets Read
A hero that fills the entire first screen with a photograph and three words of text is a common pattern and an expensive one. The visitor arrives with a question and receives an image.
What works better for a local business is a smaller hero with actual content visible on load: what you do, where you do it, and one or two specifics that distinguish you. A guarantee, a response time, a credential. The business that answers the question fastest keeps the visitor, and how long visitors stay and whether they go back to the results is a signal that matters once you are near the top of page one.
4. Images Need to Be Described, Not Just Compressed
Every image on a page is an opportunity to add a piece of information a machine can read, and most sites waste all of them.
Two fields matter. The filename, which should describe the subject rather than being a camera export like IMG_4471. And the alt text, which should describe the image plainly for someone who cannot see it. If the subject naturally includes a service and a town, include them, because that is an accurate description rather than a trick.
A page with no images at all is a separate problem. It reads as thin to both a person and a machine, and for a local business the absence of real photographs of real work is a missed credibility signal that no amount of copy compensates for.
5. Speed Is a Real Input, and the Fix Is Usually Images
Load time is a ranking input and, more importantly, a conversion input. On a phone, on a weak connection, in a parking lot, a slow page loses the customer before it has said anything.
The single largest cause on small business sites is almost always images: photographs uploaded at full camera resolution and scaled down in the browser, so the visitor downloads four megabytes to display a thumbnail. Resizing before upload, serving modern formats and deferring images below the fold fixes most of it without touching the design.
6. the Redesign Redirect Map, Which Is Where the Real Money Goes
This is the one that costs the most and gets skipped the most often.
When a site is rebuilt, URLs change. The page that ranked for years at one address now lives at another. Without a redirect from the old address to the new one, the ranking history does not transfer. It is discarded.
A redesign should begin with a crawl of the existing site, a list of which pages carry rankings and traffic, and a redirect mapped one to one from every old URL to its closest new equivalent. Not a blanket redirect to the homepage, which search engines treat as a soft error and which strands the visitor.
The reason this gets missed is organizational rather than technical. The designer frequently has no access to the search data, so has no idea which pages matter. When design and search sit with the same team the question gets asked in week one instead of discovered in month three.
The Newest One: Can a Machine Read the Page at All
There is a seventh consideration now and it is binary rather than a matter of degree.
Many modern builds assemble their content in the browser using JavaScript. Google can generally handle this. The crawlers used by AI answer engines largely cannot. They fetch the document and receive a near-empty shell.
The consequence is severe: a site built this way can rank acceptably on Google and be entirely absent from AI-generated answers, because the systems producing those answers never received any content from it. Every other item on this list is irrelevant if this one is wrong.
Testing it is simple. Fetch your own page without JavaScript and see whether your services, your town and your phone number are in what comes back. If they are not, that is the first thing to fix, ahead of everything else.
Design Decisions With Search Consequences
Most of these are made in an afternoon by somebody not thinking about search at all, and each one has a downstream effect.
|
Decision |
Search consequence |
Better default |
|
Headline as an image |
Text invisible to crawlers and assistants |
Real text, styled |
|
Content behind tabs or accordions |
Weighted less, sometimes not read |
Visible by default |
|
One long page for every service |
Nothing to rank for any single service |
A page each |
|
Fixed-width elements |
Horizontal scroll on phones |
Percentage widths |
|
Heavy hero video |
Slow first render on mobile data |
Poster image, load on interaction |
The fourth row is the one nobody catches by looking, because a viewport screenshot is only as wide as the viewport. It only shows up by comparing the document width against the screen width, which almost nobody does.
What to Check on a Phone Before Launch
|
Check |
How |
What failure looks like |
|
Sideways scroll |
Compare document width to screen width |
Content pushed off the edge |
|
Tap targets |
Try the phone number and the form |
Too small, or not tappable |
|
First screen |
Look without scrolling |
No statement of what or where |
|
Load on mobile data |
Not office wifi |
Several seconds of nothing |
|
Text size |
Read it at arm’s length |
Under about 14 pixels |
Every one of those is a five minute check and every one of them is routinely skipped, which is why so many sites that look excellent on a designer’s monitor convert poorly on the device most visitors use.
Keeping the Two Conversations Together
The fix is procedural rather than technical. The person deciding the layout needs to know which decisions carry search consequences, and the person responsible for rankings needs to see the design before it is built rather than after.
That is not a big ask. It is one meeting at the wireframe stage, and it prevents most of the table above.
Where This Leaves the Design Brief
None of the above requires an ugly site. It requires the design decisions to be made with knowledge of their downstream effects, which mostly means the person drawing the layout knowing which pages currently rank and what the site needs to say in plain HTML.
The clearest example of design decisions with downstream search effects is mobile SEO in Springfield where a layout choice can push content off the side of a phone screen unnoticed. The business profile shows the market it is written from, and there is more on how the build and the ranking connect. We have been doing local search here for more than ten years and we are veteran-owned, certified as a Service-Disabled Veteran-Owned Small Business.
If you are commissioning a redesign this year, ask for the redirect map before you approve a single mockup. It is the cheapest insurance available and almost nobody asks for it.
