What to do next on this site

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

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

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

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

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

GOAL (on workontheweb.com)
Build the definitive Work Remote cornerstone guide — on the site workontheweb.com.

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

GOAL (on workontheweb.com)
Add an interactive tool and an email capture for Work Remote — on the site workontheweb.com.

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

GOAL (on workontheweb.com)
Publish: A current, data-backed explainer in Work Remote — on the site workontheweb.com.

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

GOAL (on workontheweb.com)
Remote job boards compared, honestly and current — on the site workontheweb.com.

WHY IT MATTERS
Build the definitive comparison worksheet of remote-first job boards, WeWorkRemotely, Remote OK, FlexJobs, Wellfound, and peers, covering fees, posting volume, and vetting model, with a visible last-verified date per row. Sortable rows opening detail cards per the network pattern; jobseekers share honest comparisons far more than listicles. (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: workontheweb.com (live at https://workontheweb.com/), a Work Remote site in the WholeTech network, served from /var/www/workontheweb.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for workontheweb.com and no other site — make all changes on workontheweb.com. Act like a senior editor and web engineer who knows the Work Remote niche cold.

GOAL (on workontheweb.com)
Publish: A 'what changed in 2026' round-up for Work Remote — on the site workontheweb.com.

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

GOAL (on workontheweb.com)
Publish: The question your Work Remote audience is searching most right now — on the site workontheweb.com.

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

GOAL (on workontheweb.com)
Home-office teardowns at three budget tiers — on the site workontheweb.com.

WHY IT MATTERS
Publish complete desk-setup builds at $300, $1000, and $3000 with itemized part lists, photos or diagrams, and honest notes on what each tier sacrifices, chair quality, monitor count, mic clarity. 'Home office setup budget' queries are perennial, and the tier structure gives three distinct pages of long-tail surface. (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: workontheweb.com (live at https://workontheweb.com/), a Work Remote site in the WholeTech network, served from /var/www/workontheweb.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for workontheweb.com and no other site — make all changes on workontheweb.com. Act like a senior editor and web engineer who knows the Work Remote niche cold.

GOAL (on workontheweb.com)
Curated /videos/ page of workspace tours — on the site workontheweb.com.

WHY IT MATTERS
Assemble a /videos/ page of desk-setup tours and deep-work productivity talks, every embed verified with check-embed.mjs and dead entries dropped and renumbered. Setup-tour video is the genre this audience already binges; hosting a well-curated set keeps them on-domain and feeds the gear guides directly below each embed. (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: workontheweb.com (live at https://workontheweb.com/), a Work Remote site in the WholeTech network, served from /var/www/workontheweb.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for workontheweb.com and no other site — make all changes on workontheweb.com. Act like a senior editor and web engineer who knows the Work Remote niche cold.

GOAL (on workontheweb.com)
Work-from-anywhere guides with Travala bookings — on the site workontheweb.com.

WHY IT MATTERS
Write destination guides for remote workers, wifi reliability, timezone overlap with US teams, monthly cost of living from cited public sources, with Travala affiliate links via Impact for lodging. The digital-nomad angle extends the site beyond the home office and pairs travel-booking revenue with genuinely useful relocation research. (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: workontheweb.com (live at https://workontheweb.com/), a Work Remote site in the WholeTech network, served from /var/www/workontheweb.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for workontheweb.com and no other site — make all changes on workontheweb.com. Act like a senior editor and web engineer who knows the Work Remote niche cold.

GOAL (on workontheweb.com)
Amazon links throughout the desk-setup guides — on the site workontheweb.com.

WHY IT MATTERS
Tag every item in the budget-tier teardowns with colinfirthfan-20, monitor arms, webcams, chairs, USB mics, laptop stands, with real trade-offs stated per product rather than superlatives. Setup guides are the natural home of remote-work purchase intent; the three-tier structure captures buyers at every price point honestly. (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: workontheweb.com (live at https://workontheweb.com/), a Work Remote site in the WholeTech network, served from /var/www/workontheweb.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for workontheweb.com and no other site — make all changes on workontheweb.com. Act like a senior editor and web engineer who knows the Work Remote niche cold.

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

GOAL (on workontheweb.com)
AdSense across comparison and guide pages — on the site workontheweb.com.

WHY IT MATTERS
Enable AdSense pub-7759195213529699 on the job-board comparison, setup guides, and destination pages once content depth is real. Remote-work queries carry commercial intent (software, gear, services), which supports decent RPMs; keep the tools like the timezone calculator ad-free so their utility and linkability stay pristine. (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: workontheweb.com (live at https://workontheweb.com/), a Work Remote site in the WholeTech network, served from /var/www/workontheweb.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for workontheweb.com and no other site — make all changes on workontheweb.com. Act like a senior editor and web engineer who knows the Work Remote niche cold.

GOAL (on workontheweb.com)
Job-board rows styled as kanban tool cards — on the site workontheweb.com.

WHY IT MATTERS
Render the comparison entries as cards echoing the remote-work toolchain the audience lives in: kanban-column grouping by board type, Slack-sidebar-style navigation rail, and status-dot indicators for last-verified freshness. The interface metaphor signals instantly that this site understands how distributed teams actually work. (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: workontheweb.com (live at https://workontheweb.com/), a Work Remote site in the WholeTech network, served from /var/www/workontheweb.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for workontheweb.com and no other site — make all changes on workontheweb.com. Act like a senior editor and web engineer who knows the Work Remote niche cold.

GOAL (on workontheweb.com)
Add an FAQ answering the top questions in Work Remote — on the site workontheweb.com.

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

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

GOAL (on workontheweb.com)
Warm desk-editorial look with timezone clock strip — on the site workontheweb.com.

WHY IT MATTERS
Art-direct from the workspace itself: warm desk-photography palette (walnut, matte black, monstera green), isometric workspace illustrations for section headers, and a header strip of world clocks showing live hours across SF, Austin, London, and Manila. The site should feel like a well-lit desk, not a SaaS landing page. (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: workontheweb.com (live at https://workontheweb.com/), a Work Remote site in the WholeTech network, served from /var/www/workontheweb.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for workontheweb.com and no other site — make all changes on workontheweb.com. Act like a senior editor and web engineer who knows the Work Remote niche cold.

GOAL (on workontheweb.com)
FAQ and HowTo schema for jobseeker questions — on the site workontheweb.com.

WHY IT MATTERS
Add FAQPage schema answering 'what are the best sites to find remote jobs' and 'how do I get a remote job with no experience', plus HowTo markup on the setup teardowns. Maintain both sitemaps, ping IndexNow on publishes, and run af-deploy.py to a 90-plus score. (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: workontheweb.com (live at https://workontheweb.com/), a Work Remote site in the WholeTech network, served from /var/www/workontheweb.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for workontheweb.com and no other site — make all changes on workontheweb.com. Act like a senior editor and web engineer who knows the Work Remote niche cold.

GOAL (on workontheweb.com)
Timezone overlap calculator for distributed teams — on the site workontheweb.com.

WHY IT MATTERS
Build a client-side tool: pick two or more cities, see shaded overlap windows of mutual working hours and the best meeting slot. Distributed leads reach for exactly this weekly, and small sharp tools earn organic links and repeat direct visits that articles cannot, anchoring the whole domain's authority. (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: workontheweb.com (live at https://workontheweb.com/), a Work Remote site in the WholeTech network, served from /var/www/workontheweb.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for workontheweb.com and no other site — make all changes on workontheweb.com. Act like a senior editor and web engineer who knows the Work Remote niche cold.

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

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

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

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

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

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

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

GOAL (on workontheweb.com)
Verify affiliate links and ad placement resolve correctly — on the site workontheweb.com.

WHY IT MATTERS
Spot-check Skimlinks / Amazon links and AdSense units; remove anything broken or low-value.

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

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

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

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