HTML That Ranks: Technical SEO Basics for 2026
Technical SEO in 2026 starts with clean HTML: one H1 per page, headings nested in order, semantic tags like main, nav, and article instead of div soup, descriptive alt text on images, and fast mobile rendering. Google reads your markup before your copy, so fix the structure first.
Part of the complete SEO guide.
On this page
- Start with semantics, not keywords
- Heading hierarchy: one H1, then logic
- Meta tags that still matter (and one that doesn’t)
- Structured data is no longer optional
- Images: alt text, dimensions, and format
- Core Web Vitals in 2026
- The link tags people forget
- Where HTML ends and strategy begins
- FAQ
- Do I need to rewrite my whole site’s HTML?
- Does keyword stuffing in HTML still work?
- How often should I check my Core Web Vitals?
Most SEO problems I get hired to fix aren’t content problems. They’re HTML problems. Missing headings, bloated markup, images with no alt text, pages that take four seconds to render on a phone. Google reads your HTML before it reads your words, so if the markup is a mess, the best copy in the world won’t save you.
Here’s what actually matters in 2026, in the order I usually fix it.
Start with semantics, not keywords
HTML5 gave us real elements for real meaning. A <nav> is navigation. An <article> is a self-contained piece of content. A <main> holds the primary content of the page and should appear exactly once. These aren’t decoration. They tell crawlers and screen readers where the good stuff lives.
<body>
<header>
<nav aria-label="Main">...</nav>
</header>
<main>
<article>
<h1>Page topic</h1>
<p>The actual content.</p>
</article>
</main>
<footer>...</footer>
</body>I still see sites where the whole page is <div> soup. It renders fine. It just gives search engines nothing to hang onto. Swapping divs for semantic tags is a cheap, zero-risk win.
Heading hierarchy: one H1, then logic
One <h1> per page. It should describe the page, not the site. “Contact Us” is a fine H1 on a contact page. Your business name repeated in the H1 on every page is not.
After the H1, headings should nest in order. Don’t jump from <h2> to <h4> because the H4 “looked better.” That’s a CSS problem. Fix it with CSS.
<h1>Long Island plumber serving Suffolk County</h1>
<h2>Emergency service</h2>
<h3>What counts as an emergency</h3>
<h2>Pricing</h2>Google uses headings to understand page structure and often pulls them into featured snippets. If your headings read like an outline, you’re already ahead of most local competitors.
Meta tags that still matter (and one that doesn’t)
The <title> tag is the single highest-impact on-page element you control. Keep it under about 60 characters so it doesn’t get truncated in results, put the primary topic first, and add the location if you serve a specific area.
<title>Emergency Plumber in Commack, NY | Same-Day Service</title>
<meta name="description" content="24/7 emergency plumbing in Commack and across Long Island. Licensed, insured, upfront pricing. Call now.">
<link rel="canonical" href="https://example.com/emergency-plumber-commack/">The meta description doesn’t directly affect rankings, but it affects clicks, and clicks affect rankings. Write it like ad copy: what’s in it for the person reading it.
Skip the old keywords meta tag. Google hasn’t used it in well over a decade. It just tells your competitors what you’re targeting.
Structured data is no longer optional
Schema.org markup in JSON-LD is how you get rich results: star ratings, FAQ dropdowns, business hours, breadcrumbs. For local businesses it’s how you connect your site to your Google Business Profile.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Example Plumbing",
"telephone": "+1-631-555-0100",
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Main St",
"addressLocality": "Commack",
"addressRegion": "NY",
"postalCode": "11725"
},
"areaServed": "Long Island, NY"
}
</script>Validate it with Google’s Rich Results Test before you ship. Broken JSON-LD is worse than none, because it can trigger manual actions if you mark up things that aren’t on the page.
Images: alt text, dimensions, and format
Three things per image:
- Alt text that describes the image for someone who can’t see it. Not a keyword dump.
- Width and height attributes so the browser reserves space and the page doesn’t jump around as it loads. That layout shift is a real ranking factor.
- Modern formats. AVIF and WebP are standard now. A 2MB JPEG hero image is a self-inflicted wound.
<img src="hero.avif" alt="Technician repairing a water heater in a Commack basement"
width="1200" height="800" loading="lazy" decoding="async">Use loading="lazy" on everything below the fold. Don’t lazy-load your hero image. That delays your Largest Contentful Paint, which is one of the Core Web Vitals Google measures.
Core Web Vitals in 2026
Google’s page experience signals come down to three numbers:
- LCP (Largest Contentful Paint): under 2.5 seconds. Usually your hero image or main heading.
- INP (Interaction to Next Paint): under 200 milliseconds. Replaced First Input Delay in 2024 and measures how fast the page responds to every click, not just the first one.
- CLS (Cumulative Layout Shift): under 0.1. This is where those missing image dimensions bite you.
Run your pages through PageSpeed Insights. If INP is your problem, it’s almost always heavy JavaScript. Audit your third-party scripts. Chat widgets, tracking pixels, and one too many analytics tools will tank it.
The link tags people forget
Canonical tags prevent duplicate content issues when the same page is reachable at multiple URLs. hreflang matters if you serve multiple languages. And rel="preconnect" shaves time off third-party requests.
<link rel="canonical" href="https://example.com/services/">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>Where HTML ends and strategy begins
Clean HTML gets you indexed correctly and loads fast. It doesn’t tell you what to write about or which pages deserve your effort. That’s a different job, and it’s where Long Island SEO work picks up: keyword research, content planning, local citations, and the unglamorous link building that actually moves a small business up the map pack.
If you’d rather hand the whole thing off, most of my work is custom web development for businesses around Commack and the rest of the island. I build the markup right the first time so you’re not paying someone to fix it two years later.
FAQ
Do I need to rewrite my whole site’s HTML?
No. Start with your money pages: homepage, top service pages, contact page. Fix the title tags, heading structure, image alt text, and schema first. That’s usually 80% of the gain for a fraction of the effort.
Does keyword stuffing in HTML still work?
No, and it hasn’t for years. Hidden text, stuffed alt attributes, and keyword meta tags can get you penalized. Write for the person reading the page. Use the words they’d actually type into Google.
How often should I check my Core Web Vitals?
Quarterly for a typical small business site, and immediately after any redesign, new plugin, or new third-party script. Most performance regressions come from something you added, not something Google changed.
