Before you build a website, define the page and URL architecture around what people actually search for, make sure it loads fast on a phone, keep all important text as readable HTML rather than images, plan 301 redirects if you already have a site, add structured data and have analytics installed. Fixing these things after launch usually costs more than getting them right from the start.
- One page per service and per important city, each with a short, descriptive URL.
- Google evaluates the mobile version of your site; speed is measured with Core Web Vitals.
- Text inside images or PDFs barely counts for Google or for AI-powered search engines.
- Without 301 redirects, a redesign can wipe out the traffic you already had.
- Search Console and Google Analytics 4 go in before launch, not after.
Why SEO gets decided before design
It's common for a business to hire the design first, sign off on colors and photos, and only at the very end ask, "So how do we show up on Google?" By then, decisions have already been made that SEO can't fix without redoing work: how many pages there are, what they're called, what text they carry and what technology the site was built on.
Think of it like a house. You can repaint and swap furniture whenever you like, but moving the kitchen or adding a bathroom after the foundation is poured gets expensive. On a website, the "foundation" is the information architecture, the platform and the way content is delivered to the browser. That's why at Mercado Monkey SEO comes into a web development project in week one, not in the final week.
Fact 1: architecture and URLs matter more than the homepage design
Google ranks pages, not entire websites. If your business offers five services and they're all crammed onto a single page called "Services," you're competing with one page against five different searches. Most of the time you won't win any of them.
The rule of thumb is one page for every important search intent. An auto repair shop in Torreón, for example, should have separate pages for brakes, tune-ups, suspension and computer diagnostics, each with its own title, copy and FAQs. If it also serves the nearby cities of Gómez Palacio and Lerdo with pickup, a page per city may be worth it, as long as each one has real content and isn't a copy-paste with a different name.
- Short, descriptive URLs: /services/brakes beats /page?id=37.
- A clear hierarchy: homepage, service pages, supporting pages (guides, case studies, FAQs).
- Internal links: every important page should receive links from other pages on the site, with anchor text that describes where it leads.
- Keyword research before the sitemap: the site map comes from how people search, not from how your org chart is organized.
If you want to see how each page would look in search results before you write it, test titles and descriptions in our Google SERP preview.
Fact 2: Google looks at your site from a phone and measures speed
Google primarily indexes the mobile version of websites. If you hide text on mobile, remove sections or the menu doesn't work, that's what Google sees. In Mexico, on top of that, most of your visitors will arrive on a phone, often on mobile data rather than Wi-Fi.
Speed is evaluated with Core Web Vitals, three metrics Google publishes with clear thresholds:
| Metric | What it measures | "Good" threshold according to Google |
|---|---|---|
| LCP (Largest Contentful Paint) | How long it takes for the page's main element to appear | 2.5 seconds or less |
| INP (Interaction to Next Paint) | How quickly the page responds when you tap a button or menu | 200 milliseconds or less |
| CLS (Cumulative Layout Shift) | How much the content "jumps around" while it loads | 0.1 or less |
Speed won't make up for weak content, but it can be the tiebreaker against a similar competitor, and above all it affects sales: a slow site loses visitors before they read a word. The decisions that weigh the most are made during the build: heavy templates, sliders with ten photos, unoptimized fonts and too many plugins. We cover this in detail in our guide to Core Web Vitals and site speed.
Fact 3: if Google and AI can't read it, it doesn't exist
We still see sites where the restaurant menu is a photo, the price list is a scanned PDF and the service description lives inside a banner. To a person it looks fine; to Google and to AI-powered search engines, that information barely exists.
- Text in images: Google can read some of it with image recognition, but it doesn't treat it as main content. Write the text in HTML.
- Content that only appears with JavaScript: Google can run JavaScript, though with a delay. Many AI crawlers don't, and read only the initial HTML.
- Tabs and accordions: fine if the text is already in the HTML; bad if it only loads when the user clicks.
- Key information in a PDF: hours, service areas and FAQs belong on a regular web page.
This matters more every month, because ChatGPT, Perplexity and Gemini build their answers from what they can read on your site. If you want them to recommend you, read our guide what GEO is and how to show up in ChatGPT.
Fact 4: a redesign without 301 redirects can erase years of work
If you already have a site that gets traffic from Google, the redesign is your moment of highest risk. Every old URL that held rankings and backlinks from other sites must redirect with a 301 (permanent redirect) to the new URL that replaces it. Otherwise Google hits 404 errors, external links point to nothing and traffic drops.
The process we follow on every migration is simple, but you can't skip any step:
- Export every URL on the current site (crawl, sitemap and the pages with traffic in Search Console).
- Map each old URL to its new equivalent, one by one, not everything to the homepage.
- Keep the titles and copy that were already ranking, even if the design changes.
- Test the redirects before pointing the domain to the new server.
- Submit the new sitemap and watch for errors in Search Console over the following weeks.
An industrial distributor with a catalog of hundreds of products went through this process when it switched platforms; you can see how we handled it in the case study of the industrial distributor with an online catalog.
Fact 5: your structured data and contact details must match
Structured data (schema.org in JSON-LD format) is an invisible label that tells search engines, without ambiguity, what your business is: name, address, phone, hours, services, FAQs, reviews. It doesn't guarantee anything on its own, but it helps Google and AI understand and trust your information.
Consistency is just as important. Your name, address and phone number should be identical on your website, your Google Business Profile, Facebook and directories. Writing "1250 Independencia Blvd. East" in one place and "Independencia #1250" in another isn't a big deal; a different phone number or an address from two moves ago is.
You can generate the code with our schema generator and see which types to use in the guide to JSON-LD schema for local businesses.
Fact 6: the platform matters less than you think, but it has limits
There's no such thing as a platform that's "good for SEO" and one that's "bad." There are platforms that let you control what you need and others that make it harder. This table sums up what we see on real projects:
| Platform | Technical SEO control | Typical speed | Best for |
|---|---|---|---|
| Static site (HTML/CSS/JS) | Full | Very high | Service businesses, landing pages, sites that rarely change |
| WordPress + Elementor | High, with well-chosen plugins | Medium; depends on hosting and plugins | Teams that publish often and want to edit on their own |
| Shopify | Good, with some fixed URL rules | Good | Online stores that want to get selling fast |
| Drag-and-drop builders | Limited | Variable | Personal or very short-lived projects |
| Custom development | Full, if requested from the start | High if planned for | Portals, large catalogs, systems with user accounts |
What you should insist on, regardless of platform: the ability to edit each page's title and meta description, clean URLs, an automatic sitemap, redirect management and HTML with properly ordered headings (a single H1 per page).
Fact 7: if you don't measure from day one, you won't know what worked
Installing analytics after launch means losing the first months of data, which are exactly the ones that tell you whether the investment is on track. Before you go live, have these ready:
- Google Search Console, with the domain verified and the sitemap submitted.
- Google Analytics 4 with conversion events: WhatsApp clicks, phone clicks, form submissions, purchases.
- UTM tags on the links in your social profiles and campaigns; you can build them with the UTM builder.
In La Laguna, the Torreón metro area, a huge share of sales close over WhatsApp, so tracking clicks on the WhatsApp button is almost as important as tracking the form. Without that event, the site looks like it isn't selling even when it's generating conversations every day.
Checklist for your next meeting with the agency
Print these questions and bring them along. If whoever is going to build your site can't answer them clearly, that's a sign to ask for more detail:
- Which pages will the site have, and which searches does each one target?
- How will we measure mobile speed before launch?
- Will all the important text be in HTML, not in images?
- Who builds the redirect map if I already have a site?
- What structured data will it include, and who validates it?
- Will I be able to edit titles, descriptions and copy without depending on you?
- Which conversions will be tracked on launch day?
If you already have a site, start with a free SEO and GEO audit. If you're building from scratch, the website cost estimator helps you size the project, and the guide how long it takes to build a website in Torreón gives you realistic timelines. If you're in La Laguna, you can also see how we approach web design in Torreón.
