Hypertune · from Austin

From Austin to Kamil: SEO website changes

SEO website changes · 2 October 2026

Hi Kamil,

This is the website work from the SEO audit, agreed on the call with Bobby and Som on 2 October. It is in priority order. Things already on your list (the pricing page, the /try4free redirect, the Cloudflare crawler setting) are not repeated here, except where part of them is still open. Som and Bobby send the copy and code for items 5 and 6; you can start everything else now.

Part 1: by Friday 9 October

1Load the homepage's main image first

Why: this is the main reason the homepage is slow on phones. Google's speed test scores it 61, and the largest image appears after 6.4 seconds against Google's target of 2.5. That image is set to load late (loading="lazy"), so the browser waits before fetching it.

What to do: on the homepage's main image only, remove lazy loading and mark it as priority (the Next.js priority prop, or fetchpriority="high").

Done when: Lighthouse on the homepage no longer fails "Largest Contentful Paint image was not lazily loaded".

2One H1 heading per page

Why: Google reads the H1 as the page's main heading. /expert-tuning has eight, including the counters that read "0+", and /technology has six.

What to do: keep one H1 per page, the page's main title, and turn the others into H2s or plain text. They can look exactly the same.

Done when: each page's source has exactly one <h1>.

3Move the FAQ markup to /technology

Why: the homepage FAQ section is gone, but its hidden FAQ markup (seven questions) is still in the homepage code. Google requires the markup to match what's on the page, and Ahrefs flags it as an error.

What to do: remove the FAQPage markup from the homepage and add it to /technology, matching the FAQ there word for word.

Done when: Google's Rich Results Test finds no FAQ on the homepage and a valid FAQ on /technology.

4Four Cloudflare settings

Done when: email links on /technology are plain mailto: links, and http://www.hypertune.gg returns a 301 to https://hypertune.gg/.

5New titles, descriptions and headings (copy from Som on Wednesday 7 October)

Why: the homepage and /technology already show at positions 7 to 9 for "PC optimization for gaming" and similar searches. Better titles can move them into the top 5.

What to do: publish the titles, meta descriptions, H1s and image alt text Som sends after Bobby's check and my sign-off. This includes taking "Trusted by" out of the homepage and /tutorial search descriptions, with the wording I confirm.

Done when: the new text is in each page's source.

6Schema (code from Bobby on Wednesday 7 October)

Why: AI answers have mixed us up with hypertune.com, a different company that has shut down. This markup tells search engines which company we are and what Hypertune costs.

What to do: add the JSON-LD Bobby writes: Organization (COMPREADY Inc., logo, links to our official profiles) and the price on the existing SoftwareApplication markup.

Done when: Google's Rich Results Test shows both as valid.

7Two small fixes

Part 2: by Monday 12 October

8Redirect the pages we took out of the footer

Why: /what-hypertune-changes and /uninstall are still in Google and in the sitemap, but nothing on the site links to them any more. Their answers now live in the /technology FAQ.

What to do: permanent 301 redirects from both to /technology, and remove them from sitemap.xml in the same release. Do the same for /guides and the five guides if I confirm they go. Add lastmod dates to the sitemap.

Done when: each old address returns a 301 to /technology, and the sitemap lists only live pages.

9Retired game pages

What to do: change /game/valorant from a temporary 307 to a permanent 301. /game/fortnite and /game/rust return 404; give them a 301 to the homepage for now. When the new game pages go live, point each one at its page.

Done when: all three return a 301.

10Keep internal and affiliate addresses out of Google

Done when: Google's URL Inspection shows loggregator as excluded.

Part 3: as pages arrive, October and November

Low priority: when the templates are next touched

Thanks,

Austin