What to do next on this site

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

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

GOAL (on foreclosures.realhotsprings.com)
Build the definitive Real Estate cornerstone guide — on the site foreclosures.realhotsprings.com.

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

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

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

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

GOAL (on foreclosures.realhotsprings.com)
Add an interactive tool and an email capture for Real Estate — on the site foreclosures.realhotsprings.com.

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

GOAL (on foreclosures.realhotsprings.com)
Arkansas foreclosure-process timeline explainer — on the site foreclosures.realhotsprings.com.

WHY IT MATTERS
Publish a plain-language timeline of the Arkansas non-judicial foreclosure process, notice of default through trustee sale, with statutory citation links and typical durations. Both distressed owners and investors search this repeatedly, and the state-specific timeline is the natural cornerstone page for the subdomain. (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: foreclosures.realhotsprings.com (live at https://foreclosures.realhotsprings.com/), a Real Estate site in the WholeTech network, served from /var/www/foreclosures.realhotsprings.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for foreclosures.realhotsprings.com and no other site — make all changes on foreclosures.realhotsprings.com. Act like a senior editor and web engineer who knows the Real Estate niche cold.

GOAL (on foreclosures.realhotsprings.com)
Weekly Garland County foreclosure notice list — on the site foreclosures.realhotsprings.com.

WHY IT MATTERS
Compile the week's foreclosure and trustee-sale notices from public legal publications into a dated, structured list with address, sale date, and opening bid where published. A reliable weekly cadence turns one-time searchers into subscribers who check every posting day. (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: foreclosures.realhotsprings.com (live at https://foreclosures.realhotsprings.com/), a Real Estate site in the WholeTech network, served from /var/www/foreclosures.realhotsprings.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for foreclosures.realhotsprings.com and no other site — make all changes on foreclosures.realhotsprings.com. Act like a senior editor and web engineer who knows the Real Estate niche cold.

GOAL (on foreclosures.realhotsprings.com)
Publish: Where mortgage rates are heading and what it means for buyers now — on the site foreclosures.realhotsprings.com.

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

GOAL (on foreclosures.realhotsprings.com)
Publish: The local inventory shift — is it a buyer's or seller's market this quarter — on the site foreclosures.realhotsprings.com.

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

GOAL (on foreclosures.realhotsprings.com)
Commissioner-sale bidding guide for beginners — on the site foreclosures.realhotsprings.com.

WHY IT MATTERS
Write the step-by-step guide to bidding at Arkansas commissioner and trustee sales: registration, deposit requirements, as-is title risks, and redemption rules. First-time auction bidders are terrified of procedure mistakes, and a trustworthy walkthrough earns links from statewide investor communities. (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: foreclosures.realhotsprings.com (live at https://foreclosures.realhotsprings.com/), a Real Estate site in the WholeTech network, served from /var/www/foreclosures.realhotsprings.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for foreclosures.realhotsprings.com and no other site — make all changes on foreclosures.realhotsprings.com. Act like a senior editor and web engineer who knows the Real Estate niche cold.

GOAL (on foreclosures.realhotsprings.com)
Publish: First-time-buyer assistance & down-payment programs for 2026 — on the site foreclosures.realhotsprings.com.

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

GOAL (on foreclosures.realhotsprings.com)
Draft-only foreclosure alert subscriptions — on the site foreclosures.realhotsprings.com.

WHY IT MATTERS
Offer county foreclosure alerts where each new-notice digest is generated as a Gmail DRAFT for Paul to review and send, never auto-mailed. Subscriber leads route to Hot Springs agents under disclosed referral arrangements, monetizing the weekly list without touching the notices themselves. (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: foreclosures.realhotsprings.com (live at https://foreclosures.realhotsprings.com/), a Real Estate site in the WholeTech network, served from /var/www/foreclosures.realhotsprings.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for foreclosures.realhotsprings.com and no other site — make all changes on foreclosures.realhotsprings.com. Act like a senior editor and web engineer who knows the Real Estate niche cold.

GOAL (on foreclosures.realhotsprings.com)
Publish: How AI home-valuation tools are changing pricing — on the site foreclosures.realhotsprings.com.

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

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

GOAL (on foreclosures.realhotsprings.com)
AdSense on educational process pages — on the site foreclosures.realhotsprings.com.

WHY IT MATTERS
Run pub-7759195213529699 display units on the timeline explainer and bidding guides, keeping the weekly notice list completely ad-free. Notices are acted on under deadlines, and any visual confusion between advertisements and official links would be both unethical and trust-destroying here. (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: foreclosures.realhotsprings.com (live at https://foreclosures.realhotsprings.com/), a Real Estate site in the WholeTech network, served from /var/www/foreclosures.realhotsprings.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for foreclosures.realhotsprings.com and no other site — make all changes on foreclosures.realhotsprings.com. Act like a senior editor and web engineer who knows the Real Estate niche cold.

GOAL (on foreclosures.realhotsprings.com)
Amazon links on foreclosure investing books — on the site foreclosures.realhotsprings.com.

WHY IT MATTERS
Maintain a short honest shelf of well-regarded foreclosure and distressed-property investing books through the colinfirthfan-20 Associates tag, each with a candid one-line verdict. Keep the shelf small and genuinely useful; this audience smells padding instantly and rewards restraint with return visits. (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: foreclosures.realhotsprings.com (live at https://foreclosures.realhotsprings.com/), a Real Estate site in the WholeTech network, served from /var/www/foreclosures.realhotsprings.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for foreclosures.realhotsprings.com and no other site — make all changes on foreclosures.realhotsprings.com. Act like a senior editor and web engineer who knows the Real Estate niche cold.

GOAL (on foreclosures.realhotsprings.com)
Courthouse-docket art direction with date stamps — on the site foreclosures.realhotsprings.com.

WHY IT MATTERS
Design like a courthouse docket: legal-notice column typography, red date-stamp badges on each notice, manila-folder tab navigation between weeks, and archival off-white backgrounds. The documentary severity fits the subject and reassures visitors the site treats serious situations seriously. (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: foreclosures.realhotsprings.com (live at https://foreclosures.realhotsprings.com/), a Real Estate site in the WholeTech network, served from /var/www/foreclosures.realhotsprings.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for foreclosures.realhotsprings.com and no other site — make all changes on foreclosures.realhotsprings.com. Act like a senior editor and web engineer who knows the Real Estate niche cold.

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

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

GOAL (on foreclosures.realhotsprings.com)
Notices as sortable status worksheet — on the site foreclosures.realhotsprings.com.

WHY IT MATTERS
Present notices in the network worksheet pattern with columns for filing date, address, sale date, opening bid, and status, sortable with sticky headers and rows expanding to detail cards. Investors triage dozens of notices at once; table ergonomics are the product. (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: foreclosures.realhotsprings.com (live at https://foreclosures.realhotsprings.com/), a Real Estate site in the WholeTech network, served from /var/www/foreclosures.realhotsprings.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for foreclosures.realhotsprings.com and no other site — make all changes on foreclosures.realhotsprings.com. Act like a senior editor and web engineer who knows the Real Estate niche cold.

GOAL (on foreclosures.realhotsprings.com)
FAQ schema on Arkansas foreclosure questions — on the site foreclosures.realhotsprings.com.

WHY IT MATTERS
Add FAQPage schema answering how long Arkansas foreclosure takes, whether it is judicial or non-judicial, and what redemption rights exist, each cited to statute. Ship both sitemaps and ping IndexNow on every weekly list update so fresh notices index within hours. (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: foreclosures.realhotsprings.com (live at https://foreclosures.realhotsprings.com/), a Real Estate site in the WholeTech network, served from /var/www/foreclosures.realhotsprings.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for foreclosures.realhotsprings.com and no other site — make all changes on foreclosures.realhotsprings.com. Act like a senior editor and web engineer who knows the Real Estate niche cold.

GOAL (on foreclosures.realhotsprings.com)
Add an FAQ answering the top questions in Real Estate — on the site foreclosures.realhotsprings.com.

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

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

GOAL (on foreclosures.realhotsprings.com)
Homeowner-help resources page for distressed owners — on the site foreclosures.realhotsprings.com.

WHY IT MATTERS
Add a prominent page for owners facing foreclosure: HUD-approved counseling agencies in Arkansas, legal aid contacts, and scam warning signs, with no monetization on the page. Serving both sides of the market is honest positioning that earns links no pure investor site receives. (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: foreclosures.realhotsprings.com (live at https://foreclosures.realhotsprings.com/), a Real Estate site in the WholeTech network, served from /var/www/foreclosures.realhotsprings.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for foreclosures.realhotsprings.com and no other site — make all changes on foreclosures.realhotsprings.com. Act like a senior editor and web engineer who knows the Real Estate niche cold.

GOAL (on foreclosures.realhotsprings.com)
Add a /live/ news feed for Real Estate — on the site foreclosures.realhotsprings.com.

WHY IT MATTERS
An auto-publishing, attributed Google-News feed keeps the site fresh daily and reuses the existing GA + AdSense.

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

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

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

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

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

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

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

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

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

HOW TO APPROACH IT
1. Find 6-10 authoritative, genuinely useful Real Estate 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.