What to do next on this site

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site texasfridaynights.com.

WHY IT MATTERS
Assume a determined automated, AI-driven attacker. Enforce HTTPS, add a sensible Content-Security-Policy plus the standard security headers, eliminate open redirects and reflected user input, validate and rate-limit any form, and ensure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data — never internal or personal information.

HOW TO APPROACH IT
1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200.
2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public.
3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy).
4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A logged-out request to every sensitive path returns 403/404 — verified, not assumed.
- No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON.
- HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Verify HTTPS, security headers & a safe Agents-First surface — on the site texasfridaynights.com.

WHY IT MATTERS
Confirm the certificate is valid and HTTPS is forced, the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, CSP), and the Agents-First endpoints expose only public, non-sensitive information — trustworthy to humans and safe for the agents reading it.

HOW TO APPROACH IT
1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200.
2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public.
3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy).
4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A logged-out request to every sensitive path returns 403/404 — verified, not assumed.
- No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON.
- HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Lock down sensitive data — nothing private is publicly reachable — on the site texasfridaynights.com.

WHY IT MATTERS
Make sure a logged-out visitor or bot cannot reach anything sensitive on this site: /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404, never 200. Then scan the served HTML, JS, and JSON for leaked keys, tokens, internal emails, or personal data and remove them.

HOW TO APPROACH IT
1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200.
2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public.
3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy).
4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A logged-out request to every sensitive path returns 403/404 — verified, not assumed.
- No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON.
- HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Make the homepage genuinely distinctive — kill any generic-template feel — on the site texasfridaynights.com.

WHY IT MATTERS
Give the homepage a clear point of view, a memorable hero, and real utility above the fold. A distinctive, intentional design lifts trust, time-on-page, and the Agents-First score out of generic-template territory.

HOW TO APPROACH IT
1. Study the strongest existing pages on this topic anywhere and decide what would make THIS the single most useful page in Texas high school football — then build exactly that.
2. Write substantial, original content with a clear structure: a strong thesis up top, well-organized sections, concrete real examples and current numbers, and a decisive takeaway.
3. Ground every claim in current, authoritative sources and link out to them inline; never invent facts or statistics.
4. Wire it into the site: link from the homepage and nav, cross-link /sources/ and related pages, and add Article + FAQ schema.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The page is genuinely the strongest Texas high school football resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Build the definitive Texas high school football cornerstone guide — on the site texasfridaynights.com.

WHY IT MATTERS
Create the single most useful, authoritative page on Texas high school football anywhere — the resource the whole site points to. Deep, current, expertly structured, and link-worthy. This anchors the site's authority and is the page most likely to earn rankings and citations.

HOW TO APPROACH IT
1. Study the strongest existing pages on this topic anywhere and decide what would make THIS the single most useful page in Texas high school football — then build exactly that.
2. Write substantial, original content with a clear structure: a strong thesis up top, well-organized sections, concrete real examples and current numbers, and a decisive takeaway.
3. Ground every claim in current, authoritative sources and link out to them inline; never invent facts or statistics.
4. Wire it into the site: link from the homepage and nav, cross-link /sources/ and related pages, and add Article + FAQ schema.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The page is genuinely the strongest Texas high school football resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Add an interactive tool and an email capture for Texas high school football — on the site texasfridaynights.com.

WHY IT MATTERS
Build one genuinely useful interactive element for Texas high school football (a calculator, checklist, finder, or quiz) plus a tasteful email capture. Tools earn repeat visits, backlinks, and a first-party audience the site actually owns.

HOW TO APPROACH IT
1. Study the strongest existing pages on this topic anywhere and decide what would make THIS the single most useful page in Texas high school football — then build exactly that.
2. Write substantial, original content with a clear structure: a strong thesis up top, well-organized sections, concrete real examples and current numbers, and a decisive takeaway.
3. Ground every claim in current, authoritative sources and link out to them inline; never invent facts or statistics.
4. Wire it into the site: link from the homepage and nav, cross-link /sources/ and related pages, and add Article + FAQ schema.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The page is genuinely the strongest Texas high school football resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Publish: The Texas high school football playoff picture and the matchups to watch — on the site texasfridaynights.com.

WHY IT MATTERS
Trending angle in Texas high school football. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/.

HOW TO APPROACH IT
1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points.
2. Write a focused page: a clear thesis, the evidence, what it concretely means for a Texas high school football reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Classification schedule hubs each fall, 6A–1A — on the site texasfridaynights.com.

WHY IT MATTERS
Publish schedule and district-alignment hub pages per UIL classification every August, sourced from official UIL alignments with links, refreshed weekly through playoffs. Texas HS football search volume is enormous and brutally seasonal; owning clean classification hubs before kickoff captures the September wave every year. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Iconic Texas stadium guide series — on the site texasfridaynights.com.

WHY IT MATTERS
Profile the legendary venues — Allen's Eagle Stadium, Ratliff Stadium of Friday Night Lights fame, McKinney's palace — with capacity, history, and visiting-fan tips, cited to public records and news coverage. Stadium culture is the sport's mythology; these evergreen pages earn links from national media every time Texas stadium spending makes headlines. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Rivalry-week history features with archives — on the site texasfridaynights.com.

WHY IT MATTERS
Write researched features on the great rivalries — series histories, famous finishes — published the week each game recurs, citing newspaper archives. Rivalry weeks concentrate community search and social sharing into seven-day windows; dated features timed to them become the page alumni groups pass around. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Publish: Standout players and recruiting storylines to follow this season — on the site texasfridaynights.com.

WHY IT MATTERS
Trending angle in Texas high school football. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/.

HOW TO APPROACH IT
1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points.
2. Write a focused page: a clear thesis, the evidence, what it concretely means for a Texas high school football reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Publish: How UIL realignment and rule changes affect local programs — on the site texasfridaynights.com.

WHY IT MATTERS
Trending angle in Texas high school football. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/.

HOW TO APPROACH IT
1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points.
2. Write a focused page: a clear thesis, the evidence, what it concretely means for a Texas high school football reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Publish: Friday-night rivalries, traditions, and where to watch the games — on the site texasfridaynights.com.

WHY IT MATTERS
Trending angle in Texas high school football. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/.

HOW TO APPROACH IT
1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points.
2. Write a focused page: a clear thesis, the evidence, what it concretely means for a Texas high school football reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
College-football ticket upsell via TicketNetwork — on the site texasfridaynights.com.

WHY IT MATTERS
Add TicketNetwork affiliate modules (already live on five network sports sites) for Texas college programs on relevant pages — 'following a recruit to Austin or College Station?' framing. HS fans overlap heavily with college fandom, and college tickets are the honest inventory match since HS gates are school-sold. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
AdSense on schedule and score pages — on the site texasfridaynights.com.

WHY IT MATTERS
Run pub-7759195213529699 units across schedule hubs and stadium guides, where fall traffic concentrates. Regional advertisers and national brands bid up Texas football-adjacent inventory in season; position units between schedule tables rather than inside them so Friday-night mobile users can still scan kickoff times instantly. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Tailgate and bleacher gear, Amazon tag — on the site texasfridaynights.com.

WHY IT MATTERS
Curate a colinfirthfan-20 roundup of the Friday-night kit — stadium seats with backs, team-color blankets, portable phone chargers for filming, thermoses for late-season cold — timed to publish in August. Families attending ten-plus games a season buy exactly this list, making it the natural seasonal affiliate page. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Stadium-lights-on-turf art direction — on the site texasfridaynights.com.

WHY IT MATTERS
Design for Friday night itself: near-black backgrounds washed with stadium-light glow gradients, turf-green and chalk-white structural lines, jersey-block display numerals for scores and dates, chain-link texture accents on section edges. The site should feel like walking out of the fieldhouse under the lights, not a stats database. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point.
2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer.
3. Verify on the live render, not on a file:// preview.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Deepen the main Texas high school football guide with current data and examples — on the site texasfridaynights.com.

WHY IT MATTERS
Audit the flagship page; replace anything stale, add concrete numbers and a clear next step. Depth is what separates this from a thin template.

HOW TO APPROACH IT
1. Audit the flagship Texas high school football page and list exactly what is stale, thin, or vague.
2. Replace stale material with current data, add concrete real examples, tighten the structure, and add a clear next step for the reader.
3. Cross-link to /sources/ and the most related pages.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Depth and accuracy match the best competitor page in Texas high school football.
- No filler and no fabricated specifics — every number is current and sourced.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Build /sources/ out to at least 10 authoritative links — on the site texasfridaynights.com.

WHY IT MATTERS
Only 0 sources detected. A deep, current /sources/ page is a ranking and trust signal; pad it from the curated and popular catalogs.

HOW TO APPROACH IT
1. Open the source and confirm it is authoritative and genuinely relevant to Texas high school football.
2. Add it to /sources/ with a one-line annotation explaining why it matters, placed in the right group, with no duplicates.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The link works, is annotated and well-placed, and is a reference a real Texas high school football expert would trust.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Scoreboard-styled score and schedule modules — on the site texasfridaynights.com.

WHY IT MATTERS
Render scores and schedules as scoreboard segments — amber seven-segment-style numerals on black, HOME/VISITOR framing, quarter markers — used consistently from homepage to district pages. The scoreboard is the sport's most loaded visual object; adopting it makes every data module instantly legible and unmistakably Texas football. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point.
2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer.
3. Verify on the live render, not on a file:// preview.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Add an FAQ answering the top questions in Texas high school football — on the site texasfridaynights.com.

WHY IT MATTERS
Pull the real questions people ask in Texas high school football and answer them plainly. Mark up with FAQ schema for rich results.

HOW TO APPROACH IT
1. Audit the flagship Texas high school football page and list exactly what is stale, thin, or vague.
2. Replace stale material with current data, add concrete real examples, tighten the structure, and add a clear next step for the reader.
3. Cross-link to /sources/ and the most related pages.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Depth and accuracy match the best competitor page in Texas high school football.
- No filler and no fabricated specifics — every number is current and sourced.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
SportsEvent schema plus playoff-timing FAQ — on the site texasfridaynights.com.

WHY IT MATTERS
Mark schedule entries with SportsEvent schema and add FAQPage answering 'when do Texas high school playoffs start' and 'how do UIL districts work', updated each season. Keep both sitemaps fresh weekly in season, ping IndexNow on score updates, and hold af-deploy.py at 90+. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Playoff bracket tracker through state finals — on the site texasfridaynights.com.

WHY IT MATTERS
Build a client-side bracket page per classification, updated weekly from official results through the December state championships at AT&T Stadium. Bracket-checking is the highest-frequency fan behavior of November; a fast, mobile-first tracker becomes a daily-visit habit and the page fans bookmark all playoff season. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Apply a WT-Skins kit to lift the design and Agents-First score — on the site texasfridaynights.com.

WHY IT MATTERS
The page looks generic without a kit. Roll the cluster's kit (snapshot the old design first) to get the AF score into the 90s.

HOW TO APPROACH IT
1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point.
2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer.
3. Verify on the live render, not on a file:// preview.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Keep the live / news feed updated on cadence (2×/day) — on the site texasfridaynights.com.

WHY IT MATTERS
Confirm the cron is publishing fresh, attributed Texas high school football items and pinging IndexNow each run.

HOW TO APPROACH IT
1. Confirm or set up the auto-publishing /live/ or /news/ feed for Texas high school football: attributed, links out, and running on a 2x/day cadence.
2. Make sure each run pings IndexNow and the items are genuinely fresh and relevant.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The feed publishes fresh, correctly-attributed Texas high school football items on schedule and is discovered quickly.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Submit updated URLs via IndexNow and refresh the sitemap — on the site texasfridaynights.com.

WHY IT MATTERS
Ping IndexNow for new and changed pages so they're discovered fast; confirm the sitemap lists /act/, /sources/, /videos/.

HOW TO APPROACH IT
1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely.
2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The change validates cleanly and the affected pages are eligible for richer results or faster discovery.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Add Article + FAQ structured data — on the site texasfridaynights.com.

WHY IT MATTERS
Schema.org markup earns richer results and helps answer-engines cite the page correctly.

HOW TO APPROACH IT
1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely.
2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The change validates cleanly and the affected pages are eligible for richer results or faster discovery.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Refresh the /videos/ playlist with current, embeddable uploads — on the site texasfridaynights.com.

WHY IT MATTERS
Swap any dead or stale videos; keep only authoritative, non-clickbait Texas high school football videos. Re-verify embeds.

HOW TO APPROACH IT
1. Find 6-10 authoritative, genuinely useful Texas high school football videos that ALLOW embedding — verify each embed actually plays.
2. Curate them on /videos/ with short context, and drop anything clickbait, get-rich-quick, or low-substance.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Every embed plays, the set is authoritative and on-topic, and the page reuses the site's GA + AdSense.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Strengthen internal links between the core, /sources/ and this worksheet — on the site texasfridaynights.com.

WHY IT MATTERS
A tight internal-link web spreads authority and keeps visitors moving through the site.

HOW TO APPROACH IT
1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely.
2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The change validates cleanly and the affected pages are eligible for richer results or faster discovery.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: texasfridaynights.com (live at https://texasfridaynights.com/), a Texas high school football site in the WholeTech network, served from /var/www/texasfridaynights.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for texasfridaynights.com and no other site — make all changes on texasfridaynights.com. Act like a senior editor and web engineer who knows the Texas high school football niche cold.

GOAL (on texasfridaynights.com)
Add the network affiliate + AdSense setup — on the site texasfridaynights.com.

WHY IT MATTERS
Inject the shared Skimlinks script and the AdSense unit so existing traffic earns; one-time setup.

HOW TO APPROACH IT
1. Make the change — verify affiliate links resolve, or add the shared affiliate + AdSense setup.
2. Keep commerce low-key and well-integrated: subtle in-content links, not a bolted-on banner block.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Links resolve and can earn, and placement is tasteful and does not hurt the reading experience.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.