Yes — but usually not in the way people mean when they ask.
Design doesn't affect rankings because search engines have taste. It affects rankings because many design decisions are quietly also structural decisions, and structure is something search engines read very carefully.
Here's where the two actually meet.
Speed is a design decision before it's an engineering one
Most slow websites weren't made slow by developers. They were made slow by choices made earlier: a full-screen video header, six webfonts, a carousel of uncompressed images, an animation library imported for one effect.
Every one of those was a design decision. The engineering just honored it.
If you care about performance, the cheapest time to protect it is while the design is still a drawing. Ask what a section costs before it's built, not after.
Heading structure is the outline search engines read
A heading is not a font size. It's a statement about hierarchy.
When a page uses one h1 for its actual subject and h2s for its real sections, a search engine can reconstruct what the page covers. When headings are chosen because someone wanted that text bigger, the outline becomes noise.
This is one of the most common problems I find on existing sites, and one of the easiest to fix:
- One h1 per page, describing what the page is genuinely about
- h2s for real sections, in order, without skipping levels for visual reasons
- Size handled in CSS, independently of which tag is used
You lose nothing visually. You gain a page that can be understood.
Text inside images is invisible
If a headline, a service list, or a set of prices lives inside a JPG, it doesn't exist as far as search is concerned. It also doesn't exist for screen readers, can't be translated, can't be copied, and goes soft on high-density screens.
This shows up most often with designers who came from print, where setting type in the image is normal. On the web it's a quiet way to make your most important sentences unreadable.
Content that only exists after JavaScript runs
Search engines can execute JavaScript, but it isn't free and it isn't guaranteed to be complete. If your primary content only appears after a client-side fetch, you've made indexing conditional on something you don't control.
Server-render the content that matters. Keep JavaScript for behavior, not for the existence of your paragraphs.
Accessibility and SEO are largely the same work
This is the part I wish more people knew, because it makes the effort pay out twice.
Descriptive link text, real alt text, sensible heading order, sufficient contrast, keyboard-operable navigation — these are accessibility requirements, and they're also exactly what makes a page legible to a crawler. You're not doing two jobs. You're doing one job that counts in two places.
Design patterns that quietly cost you
A few common choices worth being deliberate about:
- Infinite scroll with no paginated fallback, which can leave most of your content unreachable
- Content hidden behind tabs or accordions that only renders on interaction
- Navigation built entirely from JavaScript handlers instead of real links
- Interstitials that cover the content someone arrived to read
- Identical page titles across a site, usually inherited from a template
None of these are exotic. I find them constantly.
What this doesn't mean
It doesn't mean designing for search engines. Sites built to please a crawler are miserable to use, and that shows up in the numbers eventually anyway.
It means recognizing that a well-structured, fast, accessible page is simultaneously the most usable version and the most indexable one. Those goals almost never conflict. When they appear to, it's usually a sign the design is asking for something it doesn't actually need.