Your website looks great. Your services are solid. Maybe you are even publishing blog posts every month. And yet, when someone in Albuquerque searches for what you do, you are nowhere on page one. Sound familiar?
Here is the uncomfortable truth we see over and over when auditing local websites: it is usually not the content that is holding them back. It is the technical foundation. A slow homepage, a stray noindex tag left over from the development phase, a sitemap pointing to pages that no longer exist. Google notices all of it, and it quietly costs you rankings, traffic, and phone calls.
The good news? Most technical SEO mistakes are detectable with free tools and fixable in an afternoon or two. In this guide, we walk through the six technical SEO mistakes we find most often on Albuquerque and New Mexico websites, and exactly how to detect and fix each one. If you would rather have a professional handle it, our SEO team does this every week, but everything below is doable in-house.
Mistake #1: Ignoring Core Web Vitals (LCP, INP, and CLS)
What it is: Core Web Vitals are Google’s three user-experience metrics: LCP (Largest Contentful Paint, how fast your main content loads), INP (Interaction to Next Paint, how fast the page responds when someone taps or clicks), and CLS (Cumulative Layout Shift, how much the page jumps around while loading). Google’s thresholds: LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1.
Why it hurts: Core Web Vitals are a confirmed ranking signal, but the business impact is bigger than the ranking impact. Research from Google and Deloitte found that improving load time by just 0.1 seconds can lift conversions by 8 to 10 percent. For a local HVAC company or law firm in Albuquerque, where a huge share of searches happen on mobile phones over cellular connections, a 6-second homepage means potential customers hit the back button and call your competitor instead.
How to detect it
- Google Search Console: open the Core Web Vitals report to see which URLs are “Poor” or “Need improvement” based on real-user data.
- PageSpeed Insights (pagespeed.web.dev): paste any URL and get both field data and lab diagnostics with specific recommendations.
- Chrome DevTools: the Performance panel now shows live LCP, INP, and CLS values as you interact with the page.
How to fix it
- For LCP: compress and properly size your hero image (WebP or AVIF format), enable caching, and use a CDN. On WordPress, a caching plugin plus an image optimizer solves most cases.
- For INP: remove or defer heavy third-party scripts. Chat widgets, tracking pixels, and slider plugins are the usual suspects on local business sites.
- For CLS: set explicit width and height on images, and reserve space for embeds and ads so nothing pushes content down mid-load.
Mistake #2: Indexation Problems Hiding in Plain Sight
What it is: Indexation problems mean Google cannot, or will not, include your pages in its index. The classic culprit is a leftover noindex tag or a “Discourage search engines” checkbox that a developer enabled during a redesign and forgot to turn off at launch. We have audited New Mexico businesses that spent months wondering why a new site got zero organic traffic, and the answer was one checkbox in WordPress Settings > Reading.
Why it hurts: A page that is not indexed cannot rank. Period. And on larger sites, wasted crawl budget (Google crawling hundreds of thin tag pages, filtered URLs, or staging leftovers) means your important service pages get crawled and refreshed less often.
How to detect it
- Search Console Page Indexing report: look at the “Why pages aren’t indexed” section. “Excluded by noindex tag” and “Blocked by robots.txt” on pages you care about are red flags.
- URL Inspection tool: paste a key service page and confirm it says “URL is on Google.”
- Site search: type site:yourdomain.com into Google. If important pages are missing, dig deeper.
- Screaming Frog SEO Spider (free up to 500 URLs): crawl your site and filter by “noindex” to catch stray tags instantly.
How to fix it
- Remove noindex tags from any page you want ranking. In WordPress, check both Settings > Reading and your SEO plugin’s per-page settings.
- Review robots.txt and make sure you are not blocking CSS, JavaScript, or entire directories Google needs.
- Deliberately noindex low-value pages (tag archives, internal search results) so crawl budget flows to pages that earn revenue.
- After fixing, use “Request Indexing” in Search Console to speed up recrawling.
Mistake #3: Canonical Tag Errors That Split Your Rankings
What it is: A canonical tag tells Google which version of a page is the “official” one when duplicates exist (http vs https, with and without trailing slash, URL parameters). Common errors include canonicals pointing to the wrong page, every page canonicalizing to the homepage, canonicals pointing to redirected or 404 URLs, and conflicting signals where the canonical says one thing and the sitemap says another.
Why it hurts: Bad canonicals split ranking signals across duplicate URLs or, worse, tell Google to ignore pages entirely. If your “Albuquerque plumbing services” page canonicalizes to your homepage, Google may never rank the service page at all, and your homepage will not rank for that query either.
How to detect it
- View source: search the HTML for rel=”canonical” on your key pages and confirm each one points to itself (the clean, https, preferred version).
- Search Console URL Inspection: compare “User-declared canonical” with “Google-selected canonical.” If they differ, Google is overriding you, and that is worth investigating.
- Screaming Frog: the Canonicals tab flags missing, non-indexable, and canonicalized URLs in one crawl.
How to fix it
- Make every indexable page self-canonical by default. Most WordPress SEO plugins do this correctly out of the box, so check for theme or plugin conflicts if they do not.
- Never canonicalize to a URL that redirects or returns a 404. Update the tag to the final destination.
- Align all your signals: canonical tags, internal links, and your XML sitemap should all reference the same URL version.
Mistake #4: JavaScript Rendering Issues Google Can’t See Past
What it is: More local sites than ever are built with JavaScript-heavy themes, page builders, or frameworks like React. Google can render JavaScript, but rendering happens in a second wave that may be delayed, and anything that fails to render (menus, product listings, service descriptions, reviews loaded via script) may simply not exist as far as Google is concerned.
Why it hurts: If your main content or internal links only appear after JavaScript executes, indexing is slower and less reliable. We have seen restaurant menus, “areas we serve” lists, and entire testimonial sections invisible to Google because they loaded client-side with no fallback. That is content and keywords doing nothing for you.
How to detect it
- Search Console URL Inspection > View Crawled Page: check the rendered HTML and screenshot. Is your main content there?
- Disable JavaScript in Chrome DevTools and reload the page. Whatever disappears is at risk.
- Google’s Rich Results Test: shows rendered HTML for any URL, no account needed.
- Screaming Frog: crawl once in text-only mode and once in JavaScript rendering mode, then compare word counts and link counts per page.
How to fix it
- Serve critical content and navigation in the initial HTML (server-side rendering or static generation) whenever possible.
- Avoid making internal links dependent on click events; use real anchor tags with href attributes.
- If a rebuild is on the table, choose a stack that renders server-side by default. Our web development team builds sites SEO-first for exactly this reason.
Mistake #5: XML Sitemap Problems That Send Google in Circles
What it is: Your XML sitemap is the roadmap you hand to Google. Common problems: sitemaps listing 404s and redirected URLs, including noindexed pages, missing important pages entirely, stale sitemaps that never update, or no sitemap submitted to Search Console at all.
Why it hurts: A dirty sitemap erodes Google’s trust in it as a signal and wastes crawl budget on dead URLs. A missing sitemap means new pages, like that blog post you published last week, take longer to be discovered. For time-sensitive local content (seasonal offers, event pages, service launches), slow discovery means missed demand.
How to detect it
- Search Console > Sitemaps: confirm a sitemap is submitted, the status is “Success,” and the discovered URL count roughly matches your real page count.
- Visit the sitemap directly (usually /sitemap.xml or /sitemap_index.xml) and spot-check URLs.
- Screaming Frog: use List mode to crawl your sitemap URLs and flag anything returning a non-200 status code or carrying a noindex tag.
How to fix it
- Use a dynamic sitemap (WordPress SEO plugins generate one automatically) so it updates when you publish or delete pages.
- Include only indexable, 200-status, canonical URLs. Nothing else belongs there.
- Submit the sitemap in Search Console and reference it in robots.txt.
Mistake #6: Botched (or Missing) Hreflang on Bilingual EN/ES Sites
What it is: This one is especially relevant here in New Mexico, where roughly one in three residents speaks Spanish at home. Many Albuquerque businesses serve customers in both English and Spanish, and a bilingual website is a genuine competitive advantage. But bilingual sites need hreflang tags: annotations that tell Google “this is the English version, this is the Spanish version of the same page.” Common mistakes include missing return tags (the English page references the Spanish one, but not vice versa), wrong language codes (using “sp” instead of “es”), pointing hreflang at noindexed or redirected URLs, and skipping the x-default tag.
Why it hurts: Without correct hreflang, Google may show your English page to a Spanish-language searcher (or the reverse), treat the two versions as competing duplicates, or rank the wrong version in the wrong market. If you serve both Albuquerque and Spain, as we do, hreflang also keeps your US English pages from cannibalizing your Spain-targeted Spanish pages.
How to detect it
- View source on both language versions and confirm each contains hreflang links to itself and to its counterpart (the “return tag” requirement).
- Screaming Frog: the Hreflang tab reports missing return links, invalid codes, and non-canonical hreflang targets.
- Search Console performance data: filter by country and see whether the right pages are getting impressions in the right markets.
How to fix it
- Use valid ISO codes: en-US for US English, es-US for US Spanish, es-ES for Spain. Language alone (en, es) works if you are not geo-targeting.
- Make hreflang bidirectional: every version must reference every other version, plus itself.
- Add an x-default pointing to your primary version for unmatched users.
- On WordPress, multilingual plugins like WPML or Polylang handle hreflang automatically once configured, so verify their output rather than hand-coding tags.
A 30-Minute Technical SEO Self-Check
Want to know where you stand right now? Run this quick pass with free tools:
- Open Search Console: check Page Indexing for unexpected exclusions and Core Web Vitals for “Poor” URLs.
- Run your homepage and top three service pages through PageSpeed Insights.
- Google site:yourdomain.com and confirm your money pages appear.
- View source on your homepage: check the canonical tag and, if bilingual, the hreflang tags.
- Load /sitemap.xml and click five random URLs. All should resolve with a 200 status.
- Disable JavaScript and reload your homepage. Confirm your content and menu still appear.
If everything checks out, great: your technical foundation is solid, and your next lever is content and links. Our local SEO checklist for Albuquerque businesses is the logical next step. If you found problems, prioritize indexation issues first (they block everything else), then Core Web Vitals, then the rest.
Why This Matters More in a Local Market
In a market the size of Albuquerque, the gap between position 3 and position 8 is often not content quality. Most local competitors publish similar pages describing similar services. The sites that win tend to be the ones that load in under 2.5 seconds on a phone, get every service page indexed cleanly, and (increasingly) serve Spanish-speaking customers properly in their own language. Technical SEO is the tiebreaker, and because so few local businesses get it right, it is also low-hanging fruit.
It also compounds with everything else you do. Faster pages convert paid traffic better, which lowers your cost per lead on Google Ads, something we break down in our comparison of Google Ads vs SEO for New Mexico businesses. Clean indexation means new content starts ranking in days instead of months. Fixing technical debt once pays dividends across every channel.
Next Steps: Get a Free Technical SEO Audit
You now have a complete playbook: six mistakes, the free tools to detect each one, and the fixes. Block off an afternoon, work through the 30-minute self-check above, and tackle issues in priority order. Most Albuquerque websites we audit have at least three of these six problems, so odds are you will find something worth fixing.
And if you would rather skip the DIY route, or you ran the checks and are not sure what the results mean, we will do it for you. Liberty Digital offers a free technical SEO audit for Albuquerque and New Mexico businesses: we crawl your site, check Core Web Vitals, indexation, canonicals, rendering, sitemaps, and hreflang, and hand you a prioritized fix list in plain English. No jargon, no obligation.
Request your free SEO audit here, and find out exactly what is standing between your website and page one.