Structured data and crawler files

Everything that has to go into the site's head and root, in the order it should be added. Replace the placeholder URLs and profile links before publishing. The entity graph is the part that matters most, and the part most sites skip.

1. Site-wide entity graph

Goes in the head of every page. The three nodes reference each other by @id, which is what makes it a graph rather than three unrelated snippets.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://example.com/#organization",
      "name": "Wiigen Console",
      "url": "https://example.com/",
      "logo": {"@type":"ImageObject","url":"https://example.com/logo.png"},
      "founder": {"@id": "https://example.com/#person"},
      "sameAs": [
        "https://www.youtube.com/@YOUR_CHANNEL",
        "https://www.reddit.com/user/YOUR_HANDLE",
        "https://github.com/YOUR_HANDLE"
      ]
    },
    {
      "@type": "WebSite",
      "@id": "https://example.com/#website",
      "url": "https://example.com/",
      "name": "Wiigen Console",
      "publisher": {"@id": "https://example.com/#organization"},
      "inLanguage": "en-US"
    },
    {
      "@type": "Person",
      "@id": "https://example.com/#person",
      "name": "YOUR NAME",
      "url": "https://example.com/about/",
      "knowsAbout": [
        "PC hardware", "graphics cards", "game console emulation",
        "handheld gaming PCs", "streaming software"
      ],
      "sameAs": [
        "https://www.linkedin.com/in/YOUR_HANDLE",
        "https://www.youtube.com/@YOUR_CHANNEL",
        "https://github.com/YOUR_HANDLE"
      ]
    }
  ]
}
</script>

2. Article schema

One per post. about and mentions name the entities the page concerns instead of leaving an engine to infer them from the prose.

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How much wattage does an RTX 4070 need?",
  "datePublished": "2026-03-04",
  "dateModified": "2026-09-18",
  "author": {"@id": "https://example.com/#person"},
  "publisher": {"@id": "https://example.com/#organization"},
  "isPartOf": {"@id": "https://example.com/#website"},
  "about": [
    {"@type": "Thing", "name": "Power supply unit sizing"},
    {"@type": "Product", "name": "NVIDIA GeForce RTX 4070"}
  ],
  "mentions": [
    {"@type": "Thing", "name": "12VHPWR connector"},
    {"@type": "Thing", "name": "GPU undervolting"}
  ]
}

3. Tool pages

A calculator is an application, not an article. Most sites mark these up as a plain page and lose the distinction.

{
  "@context": "https://schema.org",
  "@type": ["SoftwareApplication", "WebApplication"],
  "name": "PC Build Calculator",
  "url": "https://example.com/tools/build-calculator/",
  "applicationCategory": "UtilitiesApplication",
  "operatingSystem": "Any (web)",
  "description": "Checks part compatibility and estimates total system wattage and PSU size.",
  "publisher": {"@id": "https://example.com/#organization"},
  "offers": {"@type": "Offer", "price": "0", "priceCurrency": "USD"}
}

4. robots.txt

Add these before anything else. Check your CDN separately: a blanket AI-bot block there overrides whatever this file says.

User-agent: GPTBot
Allow: /

User-agent: OAI-SearchBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: Meta-ExternalAgent
Allow: /

User-agent: Bytespider
Allow: /

Sitemap: https://example.com/sitemap_index.xml

5. llms.txt

Curation, not enumeration. A plugin-generated page list defeats the point, so write the descriptions by hand and keep it under about fifty lines.

# Wiigen Console

> Independent gaming and PC hardware site covering emulation handhelds,
> budget PC builds, and the software around gaming. Modelled, estimate-based
> tools with stated margins, US-focused pricing, no sponsored content.

## Tools

- [PC Build Calculator](/tools/build-calculator/): Checks part
  compatibility and estimates total system wattage and PSU size.
- [FPS Estimator](/tools/fps-estimator/): Estimates frame-rate ranges
  from GPU tier, CPU ceiling, resolution and settings.
- [Parts Comparison](/tools/parts-comparison/): Side-by-side GPU and CPU
  comparison with tier scores and price bands.
- [Can It Run It](/tools/can-it-run-it/): Checks 31 of the most-played
  PC games against a given GPU and CPU.
- [Gamer Profile Quiz](/quiz/): Classifies a setup into one of eight
  profiles and names its weakest component.

## Guides

- [Budget PC Builds](/builds/): Complete builds from $700 to $1,500
  with the reasoning behind each part.
- [Handhelds](/handhelds/): Device recommendations organised by the
  systems they can actually run.
- [Emulation](/emulation/): Hardware requirements and settings by
  console generation.
- [Software](/software/): Capture, editing, drivers and upscaling.
- [Streaming](/streaming/): OBS settings, bitrate and capture hardware.

## About

- [About](/about/): Who writes this, how testing is done, and what
  gets disclosed.