SEO Audit

SEO audit — https://chinesegenderpredictor.app/
Score: 47.9% (grade F)
────────────────────────────────────────────────────────────

CRITICAL — fix these first
────────────────────────────────────────
1. HTTP → HTTPS redirect
   Problem: http:// version of the site serves content directly (no redirect to https).
   Why:     Serving both http and https creates duplicate content for Google and lets users land on the insecure version. It's a clear SEO and security negative.
   Fix:     Configure the web server to 301-redirect all http traffic to the https equivalent. In Nginx: add a server{} block on port 80 that does `return 301 https://$host$request_uri;`. In IIS: install the URL Rewrite module and add an HTTP-to-HTTPS rewrite rule. Consider adding a Strict-Transport-Security response header to force future visits over https.

2. www / non-www canonicalisation
   Problem: Both www and non-www versions serve content. The www variant at http://www.chinesegenderpredictor.app/ returns 200 without redirecting.
   Why:     Serving the same site under two different hosts splits your link equity in half and can trigger duplicate-content issues. This is one of the most common self-inflicted SEO wounds.
   Fix:     Pick one canonical host (recommend the one you link from more often) and 301-redirect all traffic from the other to it. In Nginx: add a `server{}` block for the non-canonical host that does `return 301 https://canonical-host$request_uri;`. In IIS: add a URL Rewrite rule.

3. Title tag
   Problem: Title is very short (16 chars).
   Why:     Short titles waste ranking opportunities — you can fit more relevant keywords in 50–60 chars.
   Fix:     Expand the title to 50–60 characters. Include your primary keyword near the start.

4. Canonical URL
   Problem: No canonical tag found.
   Why:     The canonical tag tells Google which URL is the primary version, preventing duplicate-content issues.
   Fix:     Add <link rel="canonical" href="<page-url>" /> inside <head>.

   Example:
     <link rel="canonical" href="https://chinesegenderpredictor.app/" />

5. Robots meta
   Problem: Robots meta contains noindex — this page is blocked from Google's index.
   Why:     A noindex tag excludes the page from all search engines.
   Fix:     Remove the robots meta tag, or change 'noindex' to 'index' if you want this page ranked.

6. H1 tag
   Problem: No H1 tag found on the page.
   Why:     The H1 is the page's main heading — a major signal for what the page is about.
   Fix:     Add a single <h1> tag describing the page's primary topic, 10–70 characters.

7. Word count
   Problem: Only 0 words of text content.
   Why:     Thin content is a known ranking penalty. Google typically expects 300+ words for most pages.
   Fix:     Expand the page's text content. Aim for at least 300 meaningful words.


IMPORTANT
────────────────────────────────────────
8. Meta description
   Problem: No meta description found.
   Why:     The meta description is the snippet shown under the title in search results — affects click-through rate.
   Fix:     Add <meta name="description" content="..."> inside <head>, 140–160 characters summarising the page.

   Example:
     <meta name="description" content="140–160 chars describing the page" />

9. Open Graph tags
   Problem: No Open Graph tags found.
   Why:     Without OG tags, the page shows a plain URL when shared — much lower click-through.
   Fix:     Add og:title, og:description, og:image and og:url meta tags inside <head>.

   Example:
     <meta property="og:title" content="Page title" />

     <meta property="og:description" content="Page description" />

     <meta property="og:image" content="https://example.com/preview.png" />

     <meta property="og:url" content="https://example.com/current-page" />

10. Structured data (JSON-LD)
   Problem: No schema.org JSON-LD blocks found.
   Why:     Structured data does two big jobs in 2026: it unlocks Google rich results (FAQ accordions, star ratings, price + availability cards), AND it makes your pages far more likely to be cited by AI-powered answer engines. Google AI Overviews, Perplexity, ChatGPT Search and voice assistants all prefer pages with clean schema because the entities (author, date, product, price) are unambiguously identified.
   Fix:     Add at least a WebPage or Article schema.org JSON-LD block. For product pages add Product + Offer. For how-to content add HowTo. Schema.org/docs/schemas.html lists every type.

   Example:
     <script type="application/ld+json">

     { "@context": "https://schema.org", "@type": "WebPage",

       "name": "Page Title", "url": "https://example.com/" }

     </script>

11. Link count
   Problem: No links on the page.
   Why:     Internal links help Google discover related content and distribute authority.
   Fix:     Add internal links to related pages (navigation, related articles, footer).


POLISH
────────────────────────────────────────
12. Twitter Card
   Problem: No Twitter Card meta tags found.
   Why:     Without them, Twitter/X falls back to Open Graph if present — but a proper Twitter card renders better.
   Fix:     Add <meta name="twitter:card" content="summary" /> at minimum. Also twitter:title, twitter:description, twitter:image.

   Example:
     <meta name="twitter:card" content="summary_large_image" />

     <meta name="twitter:title" content="Page title" />

     <meta name="twitter:description" content="Page description" />

     <meta name="twitter:image" content="https://example.com/preview.png" />

13. Internal linking
   Problem: Only 0 internal link(s) — page could be more connected.
   Why:     Internal links pass authority and help Google discover related pages on your site.
   Fix:     Add links from this page to at least 3 related pages on the same site (navigation, related content, in-article links).

14. Security headers
   Problem: Missing 1 of 4 recommended headers: Strict-Transport-Security.
   Why:     Security headers protect users and signal a well-maintained site.
   Fix:     Add the missing headers via your web server or CDN (Cloudflare can add them for free).

You are an SEO and HTML expert. I ran an audit on my web page and need you
to give me the exact HTML changes to apply. Don't rewrite the whole page —
only produce the specific head/body snippets I need to add or replace.

## Page being audited

- URL: https://chinesegenderpredictor.app/
- Current <title>: "Just a moment..."
- Detected language: en-US
- Page word count: 0

## Issues to fix (sorted by priority)

### 1. HTTP → HTTPS redirect — CRITICAL

- **What's wrong:** http:// version of the site serves content directly (no redirect to https).
- **Why it matters:** Serving both http and https creates duplicate content for Google and lets users land on the insecure version. It's a clear SEO and security negative.
- **What to fix:** Configure the web server to 301-redirect all http traffic to the https equivalent. In Nginx: add a server{} block on port 80 that does `return 301 https://$host$request_uri;`. In IIS: install the URL Rewrite module and add an HTTP-to-HTTPS rewrite rule. Consider adding a Strict-Transport-Security response header to force future visits over https.

### 2. www / non-www canonicalisation — CRITICAL

- **What's wrong:** Both www and non-www versions serve content. The www variant at http://www.chinesegenderpredictor.app/ returns 200 without redirecting.
- **Why it matters:** Serving the same site under two different hosts splits your link equity in half and can trigger duplicate-content issues. This is one of the most common self-inflicted SEO wounds.
- **What to fix:** Pick one canonical host (recommend the one you link from more often) and 301-redirect all traffic from the other to it. In Nginx: add a `server{}` block for the non-canonical host that does `return 301 https://canonical-host$request_uri;`. In IIS: add a URL Rewrite rule.
- **Current value:** `http://www.chinesegenderpredictor.app/`

### 3. Title tag — CRITICAL

- **What's wrong:** Title is very short (16 chars).
- **Why it matters:** Short titles waste ranking opportunities — you can fit more relevant keywords in 50–60 chars.
- **What to fix:** Expand the title to 50–60 characters. Include your primary keyword near the start.
- **Current value:** `Just a moment...`

### 4. Canonical URL — CRITICAL

- **What's wrong:** No canonical tag found.
- **Why it matters:** The canonical tag tells Google which URL is the primary version, preventing duplicate-content issues.
- **What to fix:** Add <link rel="canonical" href="<page-url>" /> inside <head>.

Reference pattern:
```html
<link rel="canonical" href="https://chinesegenderpredictor.app/" />
```

### 5. Robots meta — CRITICAL

- **What's wrong:** Robots meta contains noindex — this page is blocked from Google's index.
- **Why it matters:** A noindex tag excludes the page from all search engines.
- **What to fix:** Remove the robots meta tag, or change 'noindex' to 'index' if you want this page ranked.
- **Current value:** `noindex,nofollow`

### 6. H1 tag — CRITICAL

- **What's wrong:** No H1 tag found on the page.
- **Why it matters:** The H1 is the page's main heading — a major signal for what the page is about.
- **What to fix:** Add a single <h1> tag describing the page's primary topic, 10–70 characters.

### 7. Word count — CRITICAL

- **What's wrong:** Only 0 words of text content.
- **Why it matters:** Thin content is a known ranking penalty. Google typically expects 300+ words for most pages.
- **What to fix:** Expand the page's text content. Aim for at least 300 meaningful words.

### 8. Meta description — IMPORTANT

- **What's wrong:** No meta description found.
- **Why it matters:** The meta description is the snippet shown under the title in search results — affects click-through rate.
- **What to fix:** Add <meta name="description" content="..."> inside <head>, 140–160 characters summarising the page.

Reference pattern:
```html
<meta name="description" content="140–160 chars describing the page" />
```

### 9. Open Graph tags — IMPORTANT

- **What's wrong:** No Open Graph tags found.
- **Why it matters:** Without OG tags, the page shows a plain URL when shared — much lower click-through.
- **What to fix:** Add og:title, og:description, og:image and og:url meta tags inside <head>.

Reference pattern:
```html
<meta property="og:title" content="Page title" />
<meta property="og:description" content="Page description" />
<meta property="og:image" content="https://example.com/preview.png" />
<meta property="og:url" content="https://example.com/current-page" />
```

### 10. Structured data (JSON-LD) — IMPORTANT

- **What's wrong:** No schema.org JSON-LD blocks found.
- **Why it matters:** Structured data does two big jobs in 2026: it unlocks Google rich results (FAQ accordions, star ratings, price + availability cards), AND it makes your pages far more likely to be cited by AI-powered answer engines. Google AI Overviews, Perplexity, ChatGPT Search and voice assistants all prefer pages with clean schema because the entities (author, date, product, price) are unambiguously identified.
- **What to fix:** Add at least a WebPage or Article schema.org JSON-LD block. For product pages add Product + Offer. For how-to content add HowTo. Schema.org/docs/schemas.html lists every type.

Reference pattern:
```html
<script type="application/ld+json">
{ "@context": "https://schema.org", "@type": "WebPage",
  "name": "Page Title", "url": "https://example.com/" }
</script>
```

### 11. Link count — IMPORTANT

- **What's wrong:** No links on the page.
- **Why it matters:** Internal links help Google discover related content and distribute authority.
- **What to fix:** Add internal links to related pages (navigation, related articles, footer).

### 12. Twitter Card — POLISH

- **What's wrong:** No Twitter Card meta tags found.
- **Why it matters:** Without them, Twitter/X falls back to Open Graph if present — but a proper Twitter card renders better.
- **What to fix:** Add <meta name="twitter:card" content="summary" /> at minimum. Also twitter:title, twitter:description, twitter:image.

Reference pattern:
```html
<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:title" content="Page title" />
<meta name="twitter:description" content="Page description" />
<meta name="twitter:image" content="https://example.com/preview.png" />
```

### 13. Internal linking — POLISH

- **What's wrong:** Only 0 internal link(s) — page could be more connected.
- **Why it matters:** Internal links pass authority and help Google discover related pages on your site.
- **What to fix:** Add links from this page to at least 3 related pages on the same site (navigation, related content, in-article links).

### 14. Security headers — POLISH

- **What's wrong:** Missing 1 of 4 recommended headers: Strict-Transport-Security.
- **Why it matters:** Security headers protect users and signal a well-maintained site.
- **What to fix:** Add the missing headers via your web server or CDN (Cloudflare can add them for free).

## What I need from you

For each issue above, produce the exact HTML I should add to or replace in
the <head> or <body>, tailored to this specific page's topic and language.

Formatting rules:

1. Don't invent content that could mislead users — base replacements on the
   page's existing title, H1 and keywords shown above.
2. For the meta description, aim for 140–160 characters.
3. For titles, aim for 50–60 characters and put the primary keyword near
   the start.
4. Output one code block per fix, labelled with the issue number.
5. If a fix requires more context than shown, ask me one or two specific
   questions rather than guessing.

Do not change the visual design or the body content beyond what's requested.

## HTML output rules — every snippet must follow these

All generated HTML must be strictly valid per the HTML Living Standard. No exceptions —
the changes will be run through a conforming validator.

Document-level:
- DOCTYPE is `<!DOCTYPE html>` exactly — no legacy / XHTML doctypes, no `<?xml …?>` prolog.
- `<html>` has a BCP-47 `lang` attribute (e.g. `lang="en"`, `lang="en-GB"`).
- `<head>` starts with `<meta charset="utf-8">` (within the first 1024 bytes).
- `<head>` contains a non-empty `<title>` and `<meta name="viewport" content="width=device-width, initial-scale=1">`.

Syntax:
- All element and attribute names lowercase.
- Every attribute value wrapped in double quotes — never unquoted, never single-quoted unless the value contains a double quote.
- Void elements (`br hr img input meta link source area base col embed param track wbr`) written without a trailing slash: `<br>`, `<img …>`, `<meta …>` — never `<br />` or `<img … />`.
- Non-void elements must have an explicit closing tag: `<div></div>`, never `<div/>`.
- Boolean attributes written as the bare name: `disabled`, `required`, `readonly`, `checked` — never `disabled="disabled"` or `disabled="false"` (present = true regardless of value).
- `<script>` and `<style>` omit the redundant `type="text/javascript"` / `type="text/css"` — they are the HTML5 defaults.

Accessibility & semantics:
- Every `<img>` has an `alt` attribute. Use descriptive text for content images; `alt=""` for purely decorative ones.
- Every form control (`input` except hidden/submit/reset/button/image, `select`, `textarea`) has a programmatic label: either a wrapping `<label>`, a `<label for="id">` pointing at its id, or an `aria-label`.
- Icon-only buttons / `a[role=button]` have an `aria-label` describing the action.
- Every `id` value is unique on the page. Use classes for styling multiple elements.

Obsolete features — do not use any of the following:
- Elements: `<center>`, `<font>`, `<marquee>`, `<big>`, `<tt>`, `<strike>`, `<acronym>`, `<applet>`, `<basefont>`, `<dir>`, `<frame>`, `<frameset>`, `<noframes>`, `<blink>`. Use CSS or the semantic HTML5 equivalent instead.
- Attributes: `align`, `bgcolor`, `border`, `cellpadding`, `cellspacing`, `valign`, `frameborder`, `marginwidth`, `marginheight`, `nowrap`, `hspace`, `vspace`, `scrolling`. Replace with CSS.

Security:
- Every `<a … target="_blank">` includes `rel="noopener"` (or `rel="noopener noreferrer"`).