SEO-friendly web design: building a site Google can read.

Here is the uncomfortable truth that design portfolios never mention. Google does not see your website the way you do. It does not admire your hero animation or your custom cursor. It sends a program called Googlebot to fetch your pages, read the underlying code, and decide what each page is about and whether it deserves to rank. If that program hits a wall (a page it cannot crawl, content it cannot read, a URL that suddenly leads nowhere), the page simply falls out of the index. No warning. No apology.

The reason redesigns are so dangerous is that they change everything at once: the code, the structure, the URLs, the content, the server. Any one of those can break search visibility. All four changing on the same day is how a site that ranked on page one for years wakes up on page four. The good news is that none of this is mysterious. It comes down to a handful of decisions, and you can get every one of them right if you know to ask. Start with the most basic one: before Google can rank a page, it has to find it and reach it. That sounds obvious, and yet the most common redesign disaster is a site that looks finished but is half invisible to crawlers. A few non-negotiables make a site genuinely crawlable.

• Real links, not just buttons. Pages should connect through standard HTML links (the kind with an actual destination), not click handlers that only work when a human taps them. If a crawler cannot follow it, it does not exist.
• An honest sitemap. An XML sitemap that lists your real, current URLs gives Google a map of what matters. Submit it in Search Console after launch.
• Readable URLs. A path like /services/roof-repair tells both people and machines what the page is about. A path like /index.php?id=4837 tells them nothing.

On that last point, Google is explicit. Its URL structure guidance recommends readable words over long ID numbers, and hyphens rather than underscores to separate words, because hyphens are read as spaces between concepts and underscores are not. None of this is decorative. A clean URL is a small, permanent SEO asset, which is exactly why you should be nervous when a new design quietly rewrites all of them.

There is one more way a build can wall Google out, and it is the cruelest because it is self-inflicted. Two small things, the robots.txt file and the noindex tag, carry enormous power. Staging sites are routinely walled off with a robots.txt block or a noindex tag so the unfinished version does not show up in search. That is correct. What ruins launches is shipping those blocks to the live site. A noindex tag left on the homepage, or a robots.txt file that disallows the whole site, will methodically remove your pages from Google. It is the digital equivalent of hanging a "closed, do not enter" sign on a store that is actually open. Before launch and again right after, confirm the live site is open to crawling and nothing important is blocked. This single check has saved more rankings than any clever tactic.

For years, designers treated mobile as the smaller, simpler cousin of the real desktop site. That world is gone. Google now uses the mobile version of your pages to index and rank your site, full stop. If your phone layout is missing content that lives on desktop, that missing content effectively does not count.

The practical mandate, straight from Google's mobile-first indexing documentation, is content parity: the mobile version should contain the same text, the same headings, the same images and alt text, and the same structured data as the desktop version. This is where responsive design earns its keep. One set of content that reshapes itself to the screen avoids the trap of a stripped-down mobile site that silently hides half your words from the crawler. When a designer shows you gorgeous desktop comps and waves a hand at mobile, that is the moment to slow down and ask what gets cut on small screens. The answer should be nothing.

A slow site is a leaky bucket. Visitors bail before the page loads, and Google has folded real-world speed and stability into how it measures page experience. The metrics have names, and they are worth knowing because they turn a vague worry ("is it fast enough?") into three numbers you can put in a contract.

• Largest Contentful Paint. How long until the main content actually appears. Aim for 2.5 seconds or less.
• Interaction to Next Paint. How quickly the page responds when someone taps or clicks. Aim for 200 milliseconds or less.
• Cumulative Layout Shift. How much the page jumps around as it loads. Aim for 0.1 or less. This is the thing that makes you tap the wrong button because an ad shoved the page down.

Those thresholds come from Google's own Core Web Vitals reference on web.dev. The reason this matters during a redesign is that the flashiest design choices are usually the heaviest: enormous hero videos, dozens of custom fonts, animation libraries stacked three deep. Each one is a deposit against your speed budget. Ask your designer to show you the projected vitals on a mid-range phone over a normal connection, not on their brand-new laptop on office fiber. The gap between those two is where lost rankings hide.

Underneath the visuals, every page is built from HTML, and that HTML can be meaningful or it can be mush. Semantic HTML means using elements for what they actually are: a real heading marked as a heading, a list marked as a list, a button that is genuinely a button. This is not pedantry. It is the difference between a page Google can parse into a clear outline and a page that is one undifferentiated blob of styled boxes.

Headings deserve special attention. One clear H1 per page that states the topic, with H2s and H3s nesting logically beneath it, gives both crawlers and screen readers a table of contents for the page. The bonus is that the same structure that helps Google also helps people using assistive technology, which is why accessibility and SEO tend to rise and fall together. A site that is easy for a screen reader to navigate is usually easy for a crawler too. You do not have to choose between the two. Building it right serves both, and protects you on the legal front besides.

This is the single most expensive mistake in modern web design, and it is invisible to anyone looking only at the finished page. Many slick sites are built so that the content does not exist in the initial HTML at all. Instead, JavaScript runs in the browser and assembles the page after the fact. To a human, it looks instant and beautiful. To a crawler, the page can arrive nearly empty.

Google does render JavaScript, so this is not a flat ban. But its JavaScript SEO documentation describes a multi-step process where pages get queued for rendering separately from crawling, which can delay and complicate indexing. Google's own advice is telling: server-side rendering or pre-rendering is still a great idea, because it makes the site faster for users and crawlers alike. The same warning applies to content hidden behind clicks. Text tucked inside a tab, an accordion, or a "read more" toggle can still be indexed if it is present in the HTML, but content that loads only after a user interacts is a genuine risk. The rule of thumb: your most important words should be in the page when it first arrives, not loaded in only after a tap.

Three quieter details do more SEO work than their reputation suggests, and all three are easy to get wrong in a redesign obsessed with looks.

• Image optimization. Huge image files are the most common cause of a slow page. Compress them, serve modern formats, and size them for how they actually display. A 4,000-pixel photo squeezed into a 400-pixel slot is pure waste.
• Alt text. Every meaningful image needs a short, honest description in its alt attribute. This helps screen readers, helps image search, and gives Google context it cannot get from the pixels alone.
• Navigation and internal links. Your menu and your in-content links tell Google which pages matter and how they relate. A trendy redesign that buries the navigation behind a single hamburger icon on desktop, or strips out the internal links that used to connect your pages, can flatten the structure Google relied on to understand your site.

Internal linking is the unglamorous workhorse of SEO. The links from one page of your site to another spread authority around and help Google discover everything you publish. Preserve them through a redesign, and ideally improve them. Losing them is a silent tax you pay every month after launch.

You do not need to become an SEO to protect yourself. You need a short list of questions that separate an agency that has done this carefully from one that is about to learn on your dime. Ask these, and watch how confidently they answer.

• What happens to my URLs? If pages move, will every old URL get a permanent (301) redirect to its closest match? This is the question that prevents the most damage.
• Will you keep my current rankings in mind? Have they looked at which of my pages get organic traffic today, so those do not get deleted or buried?
• How will the content be rendered? Is the important text in the HTML, or assembled by JavaScript after load?
• What are the projected Core Web Vitals on mobile? Specific numbers, on a mid-range phone.
• Is there a launch checklist? Specifically, who confirms the noindex tags and robots blocks are removed, and who submits the new sitemap?
• Can we run old and new in parallel briefly, or at least keep a full crawl of the old site so nothing is lost?

On redirects in particular, Google's guidance on site moves with URL changes is the canonical playbook: use permanent 301 or 308 redirects, point each old URL to its true equivalent rather than dumping everything on the homepage, and keep those redirects in place for at least a year so Google can transfer the ranking signals across. If your agency cannot describe this process from memory, that is your answer.

A redesign is not the enemy. A redesign done blind is. Done well, a new site can be faster, clearer, easier to crawl, and better at converting the traffic you already earn, which is the whole point of spending the money. Done carelessly, it trades years of compounding search equity for a prettier homepage that fewer people ever find. The difference is not budget or talent. It is whether someone on the project actually cares about the plumbing as much as the paint.

So treat the questions above as your insurance policy. Bring them to whoever is pitching you, and trust the quality of the answers more than the quality of the mockups. If you would rather have a partner who builds the pretty part and the crawlable part as one job, and who treats your existing rankings as something to protect rather than bulldoze, that is the kind of work we do at Mining Wells. Either way, go in with your eyes open. The site you are about to pay for should make Google's job easier, not harder. Anything less is just a brochure with a login.