Traffic Torch SEO & UX Audit Guide

What is On-Page SEO?

On-Page SEO includes every optimization you control directly on the individual webpage to help search engines understand the topic, relevance, and value of the content. The main elements are the title tag, meta description, heading structure (H1 to H6), keyword usage in natural context, image alt attributes, internal links, and structured data (schema markup).

This area of SEO began with simple keyword placement in the late 1990s. It advanced significantly with Google's semantic shift via Hummingbird in 2013, intent understanding through RankBrain in 2015, and the strong focus on helpful, people-first content from updates that continued through 2025. In 2026 On-Page SEO is still a core direct ranking factor. It tells search engines exactly what the page offers and how well it matches user intent.

How it's tested

Traffic Torch parses the rendered HTML and evaluates these exact on-page elements in real time:

• Title tag exists, is unique, falls between 50–65 characters, and places the primary keyword early (ideally in the first 3–5 words).
• Meta description is present, unique, and sits in the ideal 120–158 character range for full display in SERPs.
• H1 heading is present, includes the target keyword or strong semantic match, and clearly states the page's main topic (only one H1 allowed).
• Structured data (JSON-LD preferred) is detected and valid for the page type (Article, WebPage, Product, FAQPage, etc.).
• Every meaningful (non-decorative) image has descriptive alt text that conveys purpose or content — decorative images use alt="".

Scoring starts at 0-100. The biggest point losses come from complete absences (no title, no meta description, no schema, missing alt text on many images). Graduated penalties apply for suboptimal length, keyword placement, or weak schema implementation.

Google’s official SEO starter guide explains title tags, meta descriptions, headings, and structured data in detail. Read Google’s SEO Starter Guide →

Quick high-impact fixes for On-Page SEO

1. Rewrite the title tag to start with the primary keyword. Keep it under 60 characters. Make it compelling for clicks.
2. Create a unique meta description between 120 and 158 characters. Include the keyword naturally. End with a clear benefit or call-to-action.
3. Align the H1 tag with the title and user intent. Use only one H1 per page.
4. Add JSON-LD structured data for the main content type. Validate it with Google's Rich Results Test.
5. Review every image. Write concise, descriptive alt text that helps both users and search engines. Avoid keyword stuffing.

What is Mobile & PWA readiness?

Mobile & PWA readiness checks whether your website delivers a flawless experience on smartphones and tablets and whether it qualifies to be installed as a Progressive Web App. This includes responsive design foundations, viewport configuration, touch-friendly elements, and PWA features such as a web app manifest, installable icons, and service worker registration.

Mobile-first indexing became Google's default in 2019. By 2026 it is non-negotiable. Google crawls, indexes, and ranks primarily using the mobile version of every page. Progressive Web Apps gained mainstream traction around 2018–2020 and continue to grow in importance because they offer app-like experiences (offline support, home screen installation, push notifications) without requiring native app store distribution.

How it's tested

Traffic Torch performs these exact client-side checks on the rendered HTML and linked resources:

• A viewport meta tag is present in with content="width=device-width, initial-scale=1" (or equivalent responsive settings) to ensure proper mobile scaling.
• A web app manifest is linked via pointing to a valid manifest.json file.
• High-resolution homescreen icons are provided — minimum 192×192 pixels, ideally also 512×512, in PNG or WebP format (checked via manifest icons array and apple-touch-icon links).
• A service worker registration is detected — looks for navigator.serviceWorker.register() calls in inline or external JavaScript.

Scoring starts at 0-100. The heaviest penalties apply for missing viewport tag (breaks responsive layout) or absent manifest (prevents installability). Smaller deductions occur for missing larger icons or undetected service worker (detection can miss dynamic registrations in minified/obfuscated code).

Google recommends mobile-first indexing and PWA best practices for modern sites. See Web.dev’s Progressive Web Apps guide →

Quick high-impact fixes for Mobile & PWA

1. Add or correct the viewport meta tag in the : . Place it early.
2. Create a manifest.json file with name, short_name, icons (at least 192 and 512 pixels), start_url, display: standalone, and theme/background colors. Link it with
3. Provide high-resolution PNG or WebP icons (192×192 and 512×512 minimum). Link them as apple-touch-icon and in the manifest.
4. Register a service worker with a simple caching strategy (even a basic one improves repeat visits). Use if ('serviceWorker' in navigator) { navigator.serviceWorker.register('/sw.js'); } in your main script.
5. Test installability with Chrome DevTools (Application tab → Manifest) and Lighthouse in incognito mode.

What is Performance regarding SEO and UX?

Performance measures how quickly and efficiently a page loads and becomes interactive for real users. Key factors include total page weight, number of requests, render-blocking resources, image optimization, font loading strategy.

Core Web Vitals became official ranking factors in 2021. By 2026 they remain critical because Google continues to prioritize real-user experience over lab data alone. Slow sites lose visitors quickly, increase bounce rates, and receive lower rankings in mobile-first indexing environments.

How it's tested

Traffic Torch analyzes the initial HTML payload and resource references with these exact client-side checks:

• HTML payload size (after minification and compression): Ideally under 120 KB to avoid bloating the initial download.
• Render-blocking resources count: Focuses on external CSS files in and synchronous (non-defer/async) JavaScript; flags when >6 as they delay First Contentful Paint.
• External font requests: Counts how many font families are loaded (Google Fonts or similar); penalizes >3 as they cause FOIT/FOUT and delay text rendering.
• Page weight contributors: Detects excessive inline styles, large inline scripts, or unoptimized markup that inflates the HTML and slows parsing/rendering.

Scoring starts at 0-100. Deductions are severity-based: heavy penalties for >12 render-blocking resources or very large payloads (>200 KB), medium for 7–12 render-blocking or 4+ fonts, and smaller for suboptimal font handling (no font-display: swap or preload).

Google’s Core Web Vitals documentation is the official source for performance thresholds and optimization. Read Google’s Core Web Vitals guide →

Quick high-impact fixes for Performance

1. Minify HTML, CSS, and JavaScript. Remove unused code and whitespace. Use tools like HTMLMinifier or build-step processors.
2. Inline critical above-the-fold CSS and defer non-critical CSS with or async loading.
3. Add defer or async attributes to non-critical script tags. Move them to the end of when possible.
4. Limit web fonts to 1–2 families. Apply font-display: swap. Preload important font files with .
5. Compress images to WebP or AVIF format. Implement lazy loading with loading="lazy" on below-the-fold images.

What is Webpage Accessibility?

Accessibility ensures that a website can be used effectively by everyone, including people with visual, auditory, motor, or cognitive impairments. Core checks cover meaningful alt text for images, proper semantic HTML structure (headings, landmarks, lists), form field labeling, sufficient color contrast, keyboard navigation, and language declaration.

Accessibility standards evolved from WCAG 1.0 in 1999 to WCAG 2.1 (2018) and WCAG 2.2 (2023). In 2026 Google increasingly treats strong accessibility as a quality signal. Poor accessibility can lead to legal risks under laws such as the ADA and EU Accessibility Act while also harming user trust and reach.

How it's tested

Traffic Torch scans the parsed DOM and runs these exact automated checks against WCAG guidelines:

• All images have appropriate alt attributes: Descriptive for content images (convey purpose/content), empty alt="" for purely decorative ones.
• The root html element includes a valid lang attribute: E.g. lang="en" or lang="en-AU" for correct language processing by screen readers and browsers.
• A main landmark exists: Either a main tag or role="main" on the primary content container to help assistive tech jump to core content.
• Heading order is logical without skips: Checks sequential hierarchy (H1 → H2 → H3 etc.) and flags jumps like H1 to H3 without H2.
• Form controls (visible inputs, textareas, selects) have programmatically associated labels: Via for/id pairing, wrapping label, aria-label, or aria-labelledby (placeholders alone do not count).

Scoring starts at 0-100. Deductions scale with violation count and severity: heaviest penalties for missing alt text on many images, absent lang attribute, or no main landmark (breaks core screen reader navigation). Medium penalties for skipped heading levels or unlabeled form fields.

Web.dev’s accessibility fundamentals cover WCAG-based checks like alt text, landmarks, and headings. Explore Web.dev Accessibility fundamentals →

Quick high-impact fixes for Accessibility

1. Add descriptive alt text to every meaningful image. Use alt="" for purely decorative images.
2. Set the correct language on the root element: html lang="en"> or your site's primary language.
3. Wrap main content in a main tag or add role="main" to the primary container.
4. Ensure headings follow a logical hierarchy. Avoid skipping levels (no H1 to H3 without H2).
5. Associate every visible form field with a label (use for/id pairs, wrapping labels, or ARIA attributes). Avoid relying on placeholders alone.

What is Content Quality?

Content Quality evaluates how well the page satisfies user intent through depth, readability, structure, originality, and scannability. It looks at word count, sentence and paragraph length, Flesch readability score, heading usage, list and table presence, and overall helpfulness of the information provided.

Content evaluation shifted dramatically after Google's Helpful Content Update (2022 onward) and continued emphasis on E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) through 2025–2026. In 2026 shallow or poorly structured content is heavily demoted. High-quality content ranks better because it keeps users engaged and answers questions comprehensively.

How it's tested

Traffic Torch extracts the visible body text and runs these exact client-side checks:

• Main content word count: Flags thin content if under 300 words (heavier penalty if under 100 words) as it often fails to satisfy user intent.
• Readability via Flesch reading ease score: Calculated from average sentence length and syllable count per word; penalizes scores below 60 (hard to read on mobile).
• Heading structure: Checks for sufficient H2/H3 usage (ideally every 300–400 words) and logical hierarchy without skips.
• Scannability elements: Detects presence of bulleted/numbered lists and tables; flags long-form pages (>500 words) without them as harder to digest.
• Complexity indicators: Measures average sentence length and syllable density to catch excessive complexity that hurts mobile reading and comprehension.

Scoring starts at 0-100. Significant penalties apply for thin content (<300 words) or very low readability (Flesch <60). Smaller deductions occur for insufficient headings, no lists/tables on longer pages, or overly complex language.

Google’s guidance on creating helpful, reliable, people-first content is the benchmark for quality evaluation. Read Google’s People-First Content guide →

Quick high-impact fixes for Content Quality

1. Expand thin pages to at least 800–1200 words for competitive topics while staying focused on user intent.
2. Shorten average sentence length to 15–20 words. Use active voice and common words to improve Flesch score above 60.
3. Add descriptive H2 and H3 headings every 300–400 words to create clear sections and improve scannability.
4. Convert key points, steps, comparisons, or features into bulleted/numbered lists. Use tables for data-heavy sections.
5. Remove fluff. Focus on original insights, examples, data, or unique angles that genuinely help the reader.

What is UX Design?

UX Design assesses how intuitive, clear, and goal-oriented the page feels to visitors. It examines primary call-to-action prominence, navigation clarity, visual hierarchy, link density, mobile touch targets, and overall flow that guides users toward desired actions without confusion or friction.

User experience signals gained ranking weight after Google's page experience update (2021) and remain important in 2026. UX design focuses on behavioral outcomes: whether users understand what to do next, stay engaged, and complete goals. Poor UX increases bounce rates and reduces conversions even on fast pages.

How it's tested

Traffic Torch evaluates interactive and structural elements with these exact client-side checks:

• Number of visible interactive elements (links, buttons, submit inputs, role="button"): Flags when >80 as it creates choice overload and decision paralysis.
• Primary calls-to-action prominence: Checks contrast ratio, button size, and placement (ideally above the fold or in clear visual hierarchy) to ensure they stand out.
• Breadcrumb navigation presence: Required on deeper pages (>2000 words or multi-level hierarchy) to show users their location and reduce disorientation.
• Link density and spacing: Penalizes excessive competing links/buttons or poor touch target spacing that overwhelms users or causes mis-taps on mobile.

Scoring starts at 0-100. Larger penalties apply to excessive interactive elements (>80) or missing breadcrumbs on complex/long pages. Smaller deductions occur for suboptimal CTA visibility, cluttered layouts, or insufficient spacing that increases friction.

Google emphasizes page experience signals including visual hierarchy, navigation, and user engagement. See Google’s Page Experience overview →

Quick high-impact fixes for UX Design

1. Reduce visible links and buttons to 1–3 primary CTAs per section. Use strong contrast, large touch targets (minimum 44×44 pixels), and action-oriented text.
2. Highlight the most important call-to-action with color, size, and placement above the fold when it matches user intent.
3. Add breadcrumb navigation on pages deeper than the homepage: Home > Category > Subcategory > Current Page.
4. Group related actions together. Move secondary links to footer, sidebar, or dropdown menus to avoid clutter.
5. Test mobile flow with real devices. Ensure tap targets do not overlap and text remains readable without zooming.

What is Website Security?

Security verifies that the page is served over a valid HTTPS connection and contains no mixed content issues. This includes checking the protocol of the main URL, all embedded resources (images, scripts, stylesheets, iframes), and the presence of a valid SSL/TLS certificate without warnings.

HTTPS became a ranking signal in 2014. By 2026 it is a baseline expectation. Browsers display "Not Secure" warnings on HTTP pages. Mixed content on HTTPS sites blocks resources and triggers warnings. These issues damage trust, increase bounce rates, and negatively affect rankings and user retention.

How it's tested

Traffic Torch inspects the protocol and all resource URLs with these exact client-side checks:

• The main page URL uses https:// (not http://): Flags full HTTP pages as insecure.
• No mixed content: Scans all embedded resources (images src, scripts src, link href, iframes, fonts) for http:// when the main page is https://.
• No insecure redirects or certificate errors: Checks the initial load context for broken HTTPS chains or invalid certificates (via browser-reported status).

Scoring starts at 0-100. The largest penalty applies to missing HTTPS (full HTTP protocol). Additional deductions trigger for any mixed content (breaks secure context, blocks features like service workers). Smaller penalties occur for redirect issues or certificate warnings that degrade trust signals.

Google recommends HTTPS everywhere and explains mixed content issues in their security guidelines. Read Google’s HTTPS and security guide →

Quick high-impact fixes for Security

1. Install a free SSL/TLS certificate through Let's Encrypt, Cloudflare, or your host. Redirect all HTTP traffic to HTTPS with a 301 permanent redirect.
2. Update every resource URL in the HTML to use https:// or relative paths (// or /). Search for http:// in the source code and replace it.
3. Fix mixed content warnings in browser console. Replace any remaining http:// links in scripts, images, iframes, or third-party embeds.
4. Enable HTTP Strict Transport Security (HSTS) with a header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload.
5. Test the site with SSL Labs (ssllabs.com) or Why No Padlock? to confirm a clean A+ grade and no mixed content.

What is Webpage Indexability?

Indexability confirms that search engines are allowed and technically able to include the page in their search results. It checks for the absence of blocking directives (no index meta tags, robots.txt disallows), the presence of a preferred canonical URL, and other crawl directives that could prevent visibility in organic search.

Indexability has been a core requirement since search engines began. In 2026 it remains essential because even perfectly optimized pages are invisible if they carry a no index tag or lack a canonical signal. Google may also choose not to index thin, duplicate, or low-value pages even without explicit blocks.

How it's tested

Traffic Torch parses the section and meta tags with these exact client-side checks:

• No meta name="robots" tag contains "no index" (checked case-insensitive in content attribute): Flags any no index directive that hides the page from search results.
• A canonical link tag exists () and points to the preferred/preferred URL version: Verifies self-referencing or correct consolidation.
• No other obvious blocking directives: Notes that client-side analysis cannot fully detect server-side x-robots-tag headers or robots.txt disallows, but flags potential issues in visible HTML.

Scoring starts at 0-100. The heaviest penalty applies to a present no index directive (explicitly removes page from search). Deductions trigger for missing canonical tag (risks duplicate content confusion and split authority). Smaller penalties apply to ambiguous or incomplete signals that could affect crawlability.

Google’s robots meta tag and canonical URL documentation covers no index, canonical, and crawl control. See Google’s Robots meta tag & canonical guide →

Quick high-impact fixes for Indexability

1. Remove any tag from production pages unless the page is intentionally private.
2. Add a self-referencing canonical tag in the : . Use the exact preferred URL.
3. Check robots.txt (via yoursite.com/robots.txt) to ensure the page path is not disallowed for User-agent: * or Googlebot.
4. After fixes request indexing in Google Search Console using the URL Inspection tool.
5. Audit staging, development, or parameter URLs to prevent accidental indexing of duplicates.

The eight pillars covered in this guide — On-Page SEO, Mobile & PWA, Performance, Accessibility, Content Quality, UX Design, Security, and Indexability — form the foundation of what modern search engines and real users reward. In 2026 Google continues to blend technical excellence with genuine user satisfaction. Sites that score highly across these areas consistently achieve better rankings, lower bounce rates, higher conversions, and stronger brand trust.

No single fix transforms everything overnight. Start with the highest-impact items: fix HTTPS and no index issues first (they can hide your pages completely), then tackle Performance and mobile readiness (direct ranking factors), and finally refine content and on-page elements for long-term authority.

The beauty of these audits lies in actionability. Each pillar gives you clear, testable signals and practical steps. Regular checks help you catch regressions early and stay ahead as algorithms evolve.

Bookmark this guide. Revisit it after major site changes or quarterly. Consistent improvement across these pillars builds compounding gains in traffic, rankings, and user loyalty.