What to do next on this site

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

GOAL (on earthscrapers.com)
Lock down sensitive data — nothing private is publicly reachable — on the site earthscrapers.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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site earthscrapers.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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Make the homepage genuinely distinctive — kill any generic-template feel — on the site earthscrapers.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 Alternative Homes — 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 Alternative Homes 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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Build the definitive Alternative Homes cornerstone guide — on the site earthscrapers.com.

WHY IT MATTERS
Create the single most useful, authoritative page on Alternative Homes 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 Alternative Homes — 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 Alternative Homes 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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Verify HTTPS, security headers & a safe Agents-First surface — on the site earthscrapers.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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Add an interactive tool and an email capture for Alternative Homes — on the site earthscrapers.com.

WHY IT MATTERS
Build one genuinely useful interactive element for Alternative Homes (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 Alternative Homes — 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 Alternative Homes 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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Case studies of real underground dwellings — on the site earthscrapers.com.

WHY IT MATTERS
Profile built examples of earth-sheltered living with sources: Coober Pedy's dugout homes, Earth-sheltered houses of the 1970s energy crisis, modern hillside builds. Real precedents ground the futurist concept and pull in the adjacent 'underground home' search traffic, which is far larger than the earthscraper term itself. (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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Publish: The 2026 cost-per-square-foot for tiny / container / ADU builds — on the site earthscrapers.com.

WHY IT MATTERS
Trending angle in Alternative Homes. 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 Alternative Homes 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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Own the definitive what-is-an-earthscraper page — on the site earthscrapers.com.

WHY IT MATTERS
Publish the canonical explainer: the inverted-skyscraper concept, the documented proposals (BNKR Arquitectura's Mexico City design foremost), why none has been built, and the engineering obstacles — all sourced. The term has steady curiosity search and no authoritative owner; the definitive page collects every citation. (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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
State-by-state can-you-build-underground guides — on the site earthscrapers.com.

WHY IT MATTERS
Practical pages on digging down legally: permit realities, egress codes, and water-table constraints summarized from public building codes for high-interest states like Texas. Serious alternative-home searchers move from dreaming to permitting questions fast, and nobody serves that transition. (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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Publish: Financing an alternative dwelling when banks balk — on the site earthscrapers.com.

WHY IT MATTERS
Trending angle in Alternative Homes. 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 Alternative Homes 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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Publish: Permitting and zoning wins that opened up this year — on the site earthscrapers.com.

WHY IT MATTERS
Trending angle in Alternative Homes. 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 Alternative Homes 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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Publish: Off-grid power kits that paid back fastest — on the site earthscrapers.com.

WHY IT MATTERS
Trending angle in Alternative Homes. 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 Alternative Homes 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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
AdSense on explainer and code pages — on the site earthscrapers.com.

WHY IT MATTERS
Run pub-7759195213529699 units on the explainer, case studies, and permitting guides where sessions are long and informational. The niche's curiosity traffic monetizes cleanly through display without compromising the site's reference tone. (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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Underground-living book and gear lists — on the site earthscrapers.com.

WHY IT MATTERS
Amazon Associates pages via colinfirthfan-20: the standard earth-sheltered construction texts, radon detectors, dehumidifiers, and sump equipment — the honest kit of below-grade living — with spec-based notes. Readers researching underground homes buy books and moisture control first; meet them there. (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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Deepen the main Alternative Homes guide with current data and examples — on the site earthscrapers.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 Alternative Homes 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 Alternative Homes.
- 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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Alt-homes newsletter with disclosed sponsors later — on the site earthscrapers.com.

WHY IT MATTERS
An occasional digest on underground and earth-sheltered building via https://wholetech.com/newsletter/widget.js — new proposals, a case study, one code insight. The alternative-housing audience is passionate and durable; a few hundred subscribers support one disclosed sponsor slot. Draft notifications only, never auto-send. (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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Architectural cutaway linework and blueprint annotations — on the site earthscrapers.com.

WHY IT MATTERS
Illustrate concepts with sectional cutaway line drawings — the earthscraper cone in elevation, an earth-sheltered home's berm profile — annotated in drafting-pen style with dimension ticks and leader lines. The architecture-competition drawing aesthetic is this subject's native visual language and photographs cannot show unbuilt ideas. (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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

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

WHY IT MATTERS
Only 2 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 Alternative Homes.
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 Alternative Homes 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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Descending-floors layout with depth meter — on the site earthscrapers.com.

WHY IT MATTERS
Structure long pages as a descent: a fixed depth meter (-10m, -20m, -35m) tracks scroll position, background strata darken through soil colors as readers go deeper, and sections read as floors of an inverted tower. The page mechanics literally perform the site's subject. (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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Honest schema answer: has one been built — on the site earthscrapers.com.

WHY IT MATTERS
Mark up a direct answer to 'has an earthscraper ever been built' — no, and here is why, with the documented proposals linked — plus FAQs on cost estimates and feasibility. Honest negatives are rare online and answer engines reward the page that states them plainly with sources. (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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Add an FAQ answering the top questions in Alternative Homes — on the site earthscrapers.com.

WHY IT MATTERS
Pull the real questions people ask in Alternative Homes and answer them plainly. Mark up with FAQ schema for rich results.

HOW TO APPROACH IT
1. Audit the flagship Alternative Homes 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 Alternative Homes.
- 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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Apply a WT-Skins kit to lift the design and Agents-First score — on the site earthscrapers.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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Interactive ground-temperature depth chart — on the site earthscrapers.com.

WHY IT MATTERS
A small static-JS interactive: slide the depth marker and watch ground temperature stabilize toward roughly 55°F year-round, with the energy-saving implication annotated from published geothermal data. It makes the core argument for building underground tangible in ten seconds and gets embedded by other sites. (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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

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

WHY IT MATTERS
Confirm the cron is publishing fresh, attributed Alternative Homes items and pinging IndexNow each run.

HOW TO APPROACH IT
1. Confirm or set up the auto-publishing /live/ or /news/ feed for Alternative Homes: 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 Alternative Homes 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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Submit updated URLs via IndexNow and refresh the sitemap — on the site earthscrapers.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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Add Article + FAQ structured data — on the site earthscrapers.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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Strengthen internal links between the core, /sources/ and this worksheet — on the site earthscrapers.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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

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

WHY IT MATTERS
Swap any dead or stale videos; keep only authoritative, non-clickbait Alternative Homes videos. Re-verify embeds.

HOW TO APPROACH IT
1. Find 6-10 authoritative, genuinely useful Alternative Homes 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: earthscrapers.com (live at https://earthscrapers.com/), a Alternative Homes site in the WholeTech network, served from /var/www/earthscrapers.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for earthscrapers.com and no other site — make all changes on earthscrapers.com. Act like a senior editor and web engineer who knows the Alternative Homes niche cold.

GOAL (on earthscrapers.com)
Add the network affiliate + AdSense setup — on the site earthscrapers.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.