Schema, Speed, and Mobile: The Boring SEO Trio That Decides Rankings

Why Technical SEO Beats Content SEO for Ties

Google’s ranking algorithm considers hundreds of factors, but at any given moment, most competing pages have roughly equivalent content quality. Someone else has written a good article on your topic. Your article is also good. Now what?

Technical SEO decides the tie.

Two pages of similar quality, one with FAQ schema, sub-2-second load time, and clean mobile experience will beat one without those three, almost every time. This is why sites that “have great content but don’t rank” often have technical SEO problems they haven’t noticed.

Technical SEO is boring. It doesn’t feel creative. Fixing it involves reading Google documentation and clicking checkboxes in your CMS. But the ROI is real: a site that dominates in content quality plus technical SEO ranks 2-3 positions higher on average than the same site with content only.

The good news: technical SEO is unlike content SEO in one important way. Content SEO is ongoing work, you need to keep publishing to keep ranking. Technical SEO is largely a one-time fix. Do it once, do it right, and you don’t have to think about it again for 12-18 months.

Schema Markup: What It Is and Why It Matters

Schema markup is structured data written in a specific format (usually JSON-LD) that tells search engines what your content actually is. Not just “this is text” but “this is a FAQ page with 5 questions” or “this is an article by X person published on Y date.”

Search engines use schema for three things:

1. Understanding. Schema helps Google understand your content faster and more accurately. Faster understanding = better indexing.
2. Rich results. Schema makes your content eligible for rich search results, those enhanced snippets with stars, images, prices, or expandable sections. Rich results get 20–30% higher click-through rates than standard blue links.
3. AI citations. AI-powered search (Google AI Overviews, ChatGPT, Perplexity) heavily uses schema to identify authoritative sources. Sites with proper schema are cited far more often in AI responses.

Which Schema Types to Add

Not every schema type is worth your time. Focus on these:

Organization, on every page. Establishes your business as a real entity.

LocalBusiness, on homepage and Contact page if you serve local customers.

Article, on every blog post. Includes headline, author, publish date.

FAQPage , on any page with an FAQ section. High-impact for AI citations.

Product / Service, on service pages. Includes name, description, price range.

BreadcrumbList, on any page nested in a hierarchy. Improves navigation display.

Review, on pages with customer testimonials that meet Google’s guidelines.

Skip VideoObject, Recipe, Event, and other niche types unless they specifically apply to your business.

Every modern CMS supports schema markup either natively (Webflow, Framer) or through plugins (WordPress with Yoast or Rank Math). If you can’t add schema through your CMS, add it manually via JSON-LD in the page head.

Page Speed: The Core Web Vitals in Plain English

Google measures page speed through Core Web Vitals, three specific metrics that map to what users experience.

LCP (Largest Contentful Paint)

What it measures: How long it takes for the biggest visible element on your page to render. Usually a hero image or headline.

Target: Under 2.5 seconds.

Common LCP killers: - Unoptimized hero images (JPEGs over 500KB) - Render-blocking JavaScript - Slow server response time (over 600ms)

Common fixes: - Convert hero images to WebP under 200KB - Preload the hero image with - Use a faster hosting provider

CLS (Cumulative Layout Shift)

What it measures: How much your page layout shifts around while loading. Elements moving after the page appears to load hurts user experience, buttons appear where images just were, and users click the wrong thing.

Target: Under 0.1.

Common CLS killers: - Images without explicit width/height attributes - Ads or embeds injecting content after page load - Fonts loading late and forcing text reflow

Common fixes: - Add width and height to every image tag - Reserve space for ads and embeds with min-height CSS - Use font-display: swap and preload critical fonts

INP (Interaction to Next Paint)

What it measures: How responsive your page is to user interactions. When someone clicks a button, how long until the page responds visibly?

Target: Under 200ms.

Common INP killers: - Heavy JavaScript blocking the main thread - Third-party scripts (chat widgets, analytics) firing synchronously - Long-running event handlers

Common fixes: - Defer non-critical JavaScript - Load third-party scripts asynchronously - Break up long tasks into smaller chunks

Test all three metrics with Google PageSpeed Insights; free, official, and reports real Chrome user data alongside lab tests. Aim for a mobile score above 70. Above 85 is best-in-class.

Mobile-First Indexing (What This Actually Means)

Google switched to mobile-first indexing in 2019 and completed the transition in 2024. What this means: Google reads and ranks your site based on the mobile version, not the desktop version.

If your desktop site is beautiful but your mobile site is broken, Google ranks you based on the broken mobile experience, not the beautiful desktop one.

Three things to verify:

1. Your mobile site has the same content as desktop. Some older sites hide content on mobile (“view on desktop for full content”). If you do this, Google can only index the mobile-visible content. Fix by showing all content on both.
2. Your mobile site is technically accessible. Google’s crawler is essentially a mobile browser. If elements are hidden behind mobile-specific issues (broken menus, missing images, unrenderable JavaScript), Google can’t index them.
3. Your mobile experience is usable. Font size above 16px on form fields (or iOS zooms). Tap targets at least 48×48 pixels. No horizontal scroll. Content readable without pinch-to-zoom.

Test mobile-friendliness with Google’s Mobile-Friendly Test; free, official, and gives specific errors to fix.

The 60-Minute Technical SEO Audit

Run through this checklist to identify what needs fixing on your site. Most items are quick to check; fixing them may take longer.

Schema (15 minutes): - [ ] Homepage has Organization schema - [ ] Every blog post has Article schema with author + publish date - [ ] Pages with FAQ have FAQPage schema - [ ] Test all schema at Google’s Rich Results Test

Speed (25 minutes): - [ ] Run PageSpeed Insights on homepage AND a service page - [ ] Mobile score above 70 on both - [ ] LCP under 2.5s - [ ] CLS under 0.1 - [ ] INP under 200ms

Mobile (20 minutes): - [ ] Test with Google Mobile-Friendly Test on 3 different page types - [ ] Load site on your actual phone; navigate every menu - [ ] Tap every CTA; verify none are too small or covered - [ ] Submit a form on mobile; verify no zoom-on-focus

Any item you can’t check off is a specific improvement worth making.

Tools Worth Using

Free (start here): - Google PageSpeed Insights; Core Web Vitals scoring - Google Rich Results Test; schema validation - Google Search Console; crawling errors and search performance - Google Mobile-Friendly Test; mobile usability - Yoast SEO or Rank Math (WordPress) plugin-based schema and speed optimizations

Paid (worth it above 10K monthly visitors): - Ahrefs or Semrush, comprehensive technical + content SEO audits – ScreamingFrog; deep site crawl for technical issues – Sitebulb, visual technical SEO audits

For most small businesses, the free tools cover 90% of what matters. Paid tools are worth it only when you have real SEO traffic to analyze.

Common Mistakes

Ignoring schema entirely. Most small business sites have zero schema markup. Adding basic schema (Organization + Article) takes an hour and lifts rankings measurably.

Focusing on desktop speed only. Google ranks based on mobile. Desktop speed is a nice-to-have; mobile speed is a must.

Not testing after making changes. Fixed something? Run PageSpeed Insights again. Half of “fixes” don’t actually fix the metric.

Chasing perfect scores. A mobile score of 92 is best-in-class. Going from 92 to 98 usually takes as much work as going from 60 to 92 and produces almost no ranking benefit.

Skipping Search Console. Google Search Console reports on real crawling issues and ranking performance. Not checking it monthly is like driving without looking at the fuel gauge.

FAQ

What is Core Web Vitals? Three metrics Google uses to measure real user experience: LCP (page load speed), CLS (visual stability), and INP (interactivity). Under 2.5 seconds LCP, under 0.1 CLS, under 200ms INP.

How do I add schema markup? Modern CMSes (Webflow, Framer) support schema natively. WordPress adds it through plugins like Yoast or Rank Math. Manual addition uses JSON-LD in the page head. Test what you add with Google’s Rich Results Test.

Does page speed matter for SEO? Yes. Since 2021, Core Web Vitals is a confirmed Google ranking factor. Sites failing Core Web Vitals rank lower than sites passing them, all else being equal.

What’s mobile-first indexing? Google reads and ranks your site based on the mobile version, not desktop. If your mobile site is broken or slower, Google ranks you based on the broken/slow experience.

Which schema types should I add? Priority: Organization (every page), Article (every blog post), FAQPage (every FAQ section), LocalBusiness (if you serve local customers). Skip niche schemas unless directly relevant.

Key Takeaways

Technical SEO decides ranking ties once content quality is roughly equal.

The three factors that matter: schema markup, Core Web Vitals speed, mobile experience.

Schema targets: Organization, Article, FAQPage, LocalBusiness (if applicable).

Speed targets: LCP under 2.5s, CLS under 0.1, INP under 200ms.

Mobile matters most: Google indexes and ranks based on mobile version.

If you’d like Octo Partners to run a full technical SEO audit and fix what’s broken on your site, that’s included in our website services. Or book a free Strategy Call, we’ll walk through the trio on your specific site and identify the biggest wins.