What to do next on this site

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

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

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

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

GOAL (on ehotsprings.com)
Build the definitive Short-Term Rentals cornerstone guide — on the site ehotsprings.com.

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

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

GOAL (on ehotsprings.com)
Add an interactive tool and an email capture for Short-Term Rentals — on the site ehotsprings.com.

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

GOAL (on ehotsprings.com)
Neighborhood-level where-to-stay guides — on the site ehotsprings.com.

WHY IT MATTERS
Guides matching stay areas to trip types: Lake Hamilton for boat weekends, downtown for Bathhouse Row walkability, Oaklawn-adjacent for race meets — with honest tradeoffs on drive times and noise. Visitors search 'where to stay in Hot Springs' endlessly and get portal listings, not local judgment. (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: ehotsprings.com (live at https://ehotsprings.com/), a Short-Term Rentals site in the WholeTech network, served from /var/www/ehotsprings.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for ehotsprings.com and no other site — make all changes on ehotsprings.com. Act like a senior editor and web engineer who knows the Short-Term Rentals niche cold.

GOAL (on ehotsprings.com)
Publish: New short-term-rental rules and how hosts should respond — on the site ehotsprings.com.

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

GOAL (on ehotsprings.com)
Season-pegged pages around recurring events — on the site ehotsprings.com.

WHY IT MATTERS
Evergreen pages built around the town's recurring calendar — Oaklawn's winter-spring racing season, summer lake season, documented festivals — each answering 'where to stay for X' and refreshed with verified dates annually. Event-anchored intent arrives in predictable waves the site can be positioned ahead of. (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: ehotsprings.com (live at https://ehotsprings.com/), a Short-Term Rentals site in the WholeTech network, served from /var/www/ehotsprings.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for ehotsprings.com and no other site — make all changes on ehotsprings.com. Act like a senior editor and web engineer who knows the Short-Term Rentals niche cold.

GOAL (on ehotsprings.com)
Terse local tourism news posts — on the site ehotsprings.com.

WHY IT MATTERS
Short dated posts in the austinmayor template on openings, attraction changes, and lodging news, each linking a primary source. A steady local pulse earns repeat direct visits and gives the neighborhood guides fresh internal links — signals a static brochure site never generates. (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: ehotsprings.com (live at https://ehotsprings.com/), a Short-Term Rentals site in the WholeTech network, served from /var/www/ehotsprings.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for ehotsprings.com and no other site — make all changes on ehotsprings.com. Act like a senior editor and web engineer who knows the Short-Term Rentals niche cold.

GOAL (on ehotsprings.com)
Publish: Dynamic-pricing tactics that actually lift occupancy in 2026 — on the site ehotsprings.com.

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

GOAL (on ehotsprings.com)
Travala booking modules on every guide — on the site ehotsprings.com.

WHY IT MATTERS
Each neighborhood and season guide carries contextual lodging links through the network's live Travala affiliate integration, placed where the stay decision crystallizes. This is the domain's core monetization fit: every reader is planning a Hot Springs trip, and the placement is service, not interruption. (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: ehotsprings.com (live at https://ehotsprings.com/), a Short-Term Rentals site in the WholeTech network, served from /var/www/ehotsprings.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for ehotsprings.com and no other site — make all changes on ehotsprings.com. Act like a senior editor and web engineer who knows the Short-Term Rentals niche cold.

GOAL (on ehotsprings.com)
Publish: The amenities guests rank highest right now — on the site ehotsprings.com.

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

GOAL (on ehotsprings.com)
Publish: Direct-booking vs. platform fees — the current math — on the site ehotsprings.com.

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

GOAL (on ehotsprings.com)
Oaklawn-trip tickets via TicketNetwork — on the site ehotsprings.com.

WHY IT MATTERS
On racing-season pages, add event-ticket links through the live TicketNetwork affiliate relationship for Oaklawn meets and touring shows at nearby venues. Racing weekends are the town's biggest stay driver; pairing tickets with lodging in one itinerary page captures both sides of the trip. (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: ehotsprings.com (live at https://ehotsprings.com/), a Short-Term Rentals site in the WholeTech network, served from /var/www/ehotsprings.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for ehotsprings.com and no other site — make all changes on ehotsprings.com. Act like a senior editor and web engineer who knows the Short-Term Rentals niche cold.

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

GOAL (on ehotsprings.com)
Mid-century motor-lodge postcard aesthetic — on the site ehotsprings.com.

WHY IT MATTERS
Art-direct from the town's golden tourist era: teal-and-coral palette, neon-sign script display type for section headers, linen-postcard texture cards, and rising-steam motifs nodding to the thermal springs. Hot Springs sells nostalgia and water; the site should feel like a 1958 vacation postcard done well. (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: ehotsprings.com (live at https://ehotsprings.com/), a Short-Term Rentals site in the WholeTech network, served from /var/www/ehotsprings.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for ehotsprings.com and no other site — make all changes on ehotsprings.com. Act like a senior editor and web engineer who knows the Short-Term Rentals niche cold.

GOAL (on ehotsprings.com)
Owner-direct listing slots for local STRs — on the site ehotsprings.com.

WHY IT MATTERS
Offer local short-term-rental owners — including the realhotsprings network's orbit — disclosed flat-fee 'featured stay' slots inside relevant neighborhood guides, with inquiry forms that create draft notifications for review before anything is sent. Owner-direct supplements the affiliate layer without misleading anyone. (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: ehotsprings.com (live at https://ehotsprings.com/), a Short-Term Rentals site in the WholeTech network, served from /var/www/ehotsprings.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for ehotsprings.com and no other site — make all changes on ehotsprings.com. Act like a senior editor and web engineer who knows the Short-Term Rentals niche cold.

GOAL (on ehotsprings.com)
Stays as sortable worksheet with detail cards — on the site ehotsprings.com.

WHY IT MATTERS
Present stay options as a sortable table per the alldomains DB model — area, sleeps, lake access, walk-to-downtown columns — with rows opening detail cards. Trip planners comparing options think in comparison tables; the format also showcases honest tradeoffs the guides promise. (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: ehotsprings.com (live at https://ehotsprings.com/), a Short-Term Rentals site in the WholeTech network, served from /var/www/ehotsprings.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for ehotsprings.com and no other site — make all changes on ehotsprings.com. Act like a senior editor and web engineer who knows the Short-Term Rentals niche cold.

GOAL (on ehotsprings.com)
Add an FAQ answering the top questions in Short-Term Rentals — on the site ehotsprings.com.

WHY IT MATTERS
Pull the real questions people ask in Short-Term Rentals and answer them plainly. Mark up with FAQ schema for rich results.

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

GOAL (on ehotsprings.com)
Schema answers for best-area-to-stay queries — on the site ehotsprings.com.

WHY IT MATTERS
Publish 40-word FAQ-schema answers for 'best area to stay in Hot Springs Arkansas', 'should I stay downtown or on Lake Hamilton', and 'when is Oaklawn racing season' with verified dates. Run af-deploy.py into the 90s so trip-planning agents cite ehotsprings directly. (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: ehotsprings.com (live at https://ehotsprings.com/), a Short-Term Rentals site in the WholeTech network, served from /var/www/ehotsprings.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for ehotsprings.com and no other site — make all changes on ehotsprings.com. Act like a senior editor and web engineer who knows the Short-Term Rentals niche cold.

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

GOAL (on ehotsprings.com)
Season-by-season trip-cost explainer chart — on the site ehotsprings.com.

WHY IT MATTERS
A simple chart page assembling public lodging-rate patterns by season — racing season premiums, summer lake peaks, shoulder-month values — with honest sourcing and a dataviz-standard figure. 'When is Hot Springs cheapest' is a durable query, and the chart earns embeds from trip forums. (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: ehotsprings.com (live at https://ehotsprings.com/), a Short-Term Rentals site in the WholeTech network, served from /var/www/ehotsprings.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for ehotsprings.com and no other site — make all changes on ehotsprings.com. Act like a senior editor and web engineer who knows the Short-Term Rentals niche cold.

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

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

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

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

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

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

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

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