A prioritized, living to-do list for jane.austen.com, built from this site's sources and current trends in Literature. Click any row for the why & a ready-to-paste prompt — hit Copy prompt and paste it straight into your AI agent. Click a column header to sort.
| No | Rank | Cat | Date | Action |
|---|---|---|---|---|
| 1 | 99 | Security | 2026-06-19 | on jane.austen.com Make the site mythos-attack-proof — harden against automated & AI-agent abuse |
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. ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site jane.austen.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. | ||||
| 2 | 98 | Flagship | 2026-06-20 | on jane.austen.com Build the definitive Literature cornerstone guide |
Create the single most useful, authoritative page on Literature 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. ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Build the definitive Literature cornerstone guide — on the site jane.austen.com. WHY IT MATTERS Create the single most useful, authoritative page on Literature 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 Literature — 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 Literature 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. | ||||
| 3 | 98 | Security | 2026-06-20 | on jane.austen.com Lock down sensitive data — nothing private is publicly reachable |
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. ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Lock down sensitive data — nothing private is publicly reachable — on the site jane.austen.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. | ||||
| 4 | 97 | Security | 2026-06-21 | on jane.austen.com Verify HTTPS, security headers & a safe Agents-First surface |
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. ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Verify HTTPS, security headers & a safe Agents-First surface — on the site jane.austen.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. | ||||
| 5 | 91 | Flagship | 2026-06-25 | on jane.austen.com Make the homepage genuinely distinctive — kill any generic-template feel |
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. ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Make the homepage genuinely distinctive — kill any generic-template feel — on the site jane.austen.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 Literature — 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 Literature 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. | ||||
| 6 | 90 | Flagship | 2026-06-26 | on jane.austen.com Add an interactive tool and an email capture for Literature |
Build one genuinely useful interactive element for Literature (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. ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Add an interactive tool and an email capture for Literature — on the site jane.austen.com. WHY IT MATTERS Build one genuinely useful interactive element for Literature (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 Literature — 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 Literature 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. | ||||
| 7 | 90 | Trends | 2026-06-26 | on jane.austen.com Publish: The adaptations bringing classic works back to readers |
Trending angle in Literature. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/. ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Publish: The adaptations bringing classic works back to readers — on the site jane.austen.com. WHY IT MATTERS Trending angle in Literature. 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 Literature 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. | ||||
| 8 | 89 | Popularity | 2026-06-26 | on jane.austen.com Publish chapter-by-chapter Austen reading guides |
Build reading guides for each novel — chapter summaries, character maps, Regency context notes — over the public-domain texts. Students and book clubs search chapter-level Austen queries year-round in enormous volume, and an austen.com subdomain carries instant name-match authority most literature sites would kill for. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Publish chapter-by-chapter Austen reading guides — on the site jane.austen.com. WHY IT MATTERS Build reading guides for each novel — chapter summaries, character maps, Regency context notes — over the public-domain texts. Students and book clubs search chapter-level Austen queries year-round in enormous volume, and an austen.com subdomain carries instant name-match authority most literature sites would kill for. (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. | ||||
| 9 | 85 | Trends | 2026-06-29 | on jane.austen.com Publish: Public-domain works newly freed this year |
Trending angle in Literature. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/. ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Publish: Public-domain works newly freed this year — on the site jane.austen.com. WHY IT MATTERS Trending angle in Literature. 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 Literature 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. | ||||
| 10 | 84 | Trends | 2026-06-30 | on jane.austen.com Publish: Reading-challenge and book-club angles that draw traffic |
Trending angle in Literature. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/. ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Publish: Reading-challenge and book-club angles that draw traffic — on the site jane.austen.com. WHY IT MATTERS Trending angle in Literature. 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 Literature 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. | ||||
| 11 | 83 | Popularity | 2026-06-30 | on jane.austen.com Compare screen adaptations novel by novel |
Create adaptation-comparison pages — the 1995 versus 2005 Pride and Prejudice treatments, Emma's four screen versions — judged scene by scene against the text. Adaptation debates drive perennial search and social traffic, and every new streaming Austen production sends fresh waves to whoever already owns the comparison. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Compare screen adaptations novel by novel — on the site jane.austen.com. WHY IT MATTERS Create adaptation-comparison pages — the 1995 versus 2005 Pride and Prejudice treatments, Emma's four screen versions — judged scene by scene against the text. Adaptation debates drive perennial search and social traffic, and every new streaming Austen production sends fresh waves to whoever already owns the comparison. (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. | ||||
| 12 | 80 | Popularity | 2026-07-03 | on jane.austen.com Maintain real-world Austen events calendar |
Keep a dated calendar of genuine Austen-world events — JASNA's Annual General Meeting, Bath's Jane Austen Festival, Chawton House programs — sourced from the organizations' own announcements. Event queries recur annually, and a maintained calendar earns links from regional Janeite societies looking for a canonical list. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Maintain real-world Austen events calendar — on the site jane.austen.com. WHY IT MATTERS Keep a dated calendar of genuine Austen-world events — JASNA's Annual General Meeting, Bath's Jane Austen Festival, Chawton House programs — sourced from the organizations' own announcements. Event queries recur annually, and a maintained calendar earns links from regional Janeite societies looking for a canonical list. (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. | ||||
| 13 | 78 | Revenue | 2026-07-04 | on jane.austen.com Add Travala links for literary pilgrimages |
On pages covering Bath, Chawton, and Winchester, add Travala hotel deep links through the live Impact integration — 'staying near the Jane Austen Centre' modules. Literary pilgrimage is real, planned travel; readers researching festival trips book rooms, making travel affiliate the honest monetization for place pages. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Add Travala links for literary pilgrimages — on the site jane.austen.com. WHY IT MATTERS On pages covering Bath, Chawton, and Winchester, add Travala hotel deep links through the live Impact integration — 'staying near the Jane Austen Centre' modules. Literary pilgrimage is real, planned travel; readers researching festival trips book rooms, making travel affiliate the honest monetization for place pages. (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. | ||||
| 14 | 77 | Trends | 2026-07-05 | on jane.austen.com Publish: Annotated / accessible editions worth featuring |
Trending angle in Literature. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/. ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Publish: Annotated / accessible editions worth featuring — on the site jane.austen.com. WHY IT MATTERS Trending angle in Literature. 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 Literature 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. | ||||
| 15 | 76 | Revenue | 2026-07-05 | on jane.austen.com Curate editions and adaptations with Amazon |
Publish annotated buying guides to Austen editions — annotated scholarly sets, gift hardbacks, audiobook narrators compared — plus adaptation DVDs and streams, with Amazon tag colinfirthfan-20. The tag's very name comes from this fandom; this is its single most natural, highest-converting home on the network. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Curate editions and adaptations with Amazon — on the site jane.austen.com. WHY IT MATTERS Publish annotated buying guides to Austen editions — annotated scholarly sets, gift hardbacks, audiobook narrators compared — plus adaptation DVDs and streams, with Amazon tag colinfirthfan-20. The tag's very name comes from this fandom; this is its single most natural, highest-converting home on the network. (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. | ||||
| 16 | 76 | Revenue | 2026-07-05 | on jane.austen.com Run gentle AdSense on study pages |
Enable shared AdSense pub-7759195213529699 on high-traffic study and summary pages where education advertisers bid steadily, keeping the reading-experience pages themselves clean. Students tolerate modest ads around study aids; readers mid-chapter deserve typographic calm — split the treatment and both audiences stay. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Run gentle AdSense on study pages — on the site jane.austen.com. WHY IT MATTERS Enable shared AdSense pub-7759195213529699 on high-traffic study and summary pages where education advertisers bid steadily, keeping the reading-experience pages themselves clean. Students tolerate modest ads around study aids; readers mid-chapter deserve typographic calm — split the treatment and both audiences stay. (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. | ||||
| 17 | 72 | Design | 2026-07-08 | on jane.austen.com Adopt Regency letterpress art direction |
Design from Austen's material world: letterpress-style serif typography, duck-egg and muslin palette, wax-seal motifs for section marks, and cross-hatched illustration in the Hugh Thomson tradition. Pages should feel like a fine Regency-era printing, unmistakably Austen before the first sentence is read. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Adopt Regency letterpress art direction — on the site jane.austen.com. WHY IT MATTERS Design from Austen's material world: letterpress-style serif typography, duck-egg and muslin palette, wax-seal motifs for section marks, and cross-hatched illustration in the Hugh Thomson tradition. Pages should feel like a fine Regency-era printing, unmistakably Austen before the first sentence is read. (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. | ||||
| 18 | 71 | Content | 2026-07-09 | on jane.austen.com Deepen the main Literature guide with current data and examples |
Audit the flagship page; replace anything stale, add concrete numbers and a clear next step. Depth is what separates this from a thin template. ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Deepen the main Literature guide with current data and examples — on the site jane.austen.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 Literature 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 Literature. - 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. | ||||
| 19 | 71 | Sources | 2026-07-09 | on jane.austen.com Build /sources/ out to at least 10 authoritative links |
Only 2 sources detected. A deep, current /sources/ page is a ranking and trust signal; pad it from the curated and popular catalogs. ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Build /sources/ out to at least 10 authoritative links — on the site jane.austen.com. WHY IT MATTERS Only 2 sources detected. A deep, current /sources/ page is a ranking and trust signal; pad it from the curated and popular catalogs. HOW TO APPROACH IT 1. Open the source and confirm it is authoritative and genuinely relevant to Literature. 2. Add it to /sources/ with a one-line annotation explaining why it matters, placed in the right group, with no duplicates. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The link works, is annotated and well-placed, and is a reference a real Literature expert would trust. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 20 | 70 | Design | 2026-07-10 | on jane.austen.com Set chapter pages as epistolary letters |
Lay out reading-guide pages like period correspondence — generous margins, drop caps, dateline headers, a folded-letter card motif for chapter navigation. Austen's novels breathe through letters; an epistolary page design makes long study content feel in-world rather than like a homework database. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Set chapter pages as epistolary letters — on the site jane.austen.com. WHY IT MATTERS Lay out reading-guide pages like period correspondence — generous margins, drop caps, dateline headers, a folded-letter card motif for chapter navigation. Austen's novels breathe through letters; an epistolary page design makes long study content feel in-world rather than like a homework database. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point. 2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer. 3. Verify on the live render, not on a file:// preview. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 21 | 67 | AEO | 2026-07-12 | on jane.austen.com Add FAQ schema on reading order |
Mark up FAQPage entries for 'what order to read Jane Austen', 'when was each novel published', and 'which adaptation is most faithful', each answered concisely with sources. These evergreen questions saturate answer engines, and the austen.com domain name makes its structured answers unusually credible citations. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Add FAQ schema on reading order — on the site jane.austen.com. WHY IT MATTERS Mark up FAQPage entries for 'what order to read Jane Austen', 'when was each novel published', and 'which adaptation is most faithful', each answered concisely with sources. These evergreen questions saturate answer engines, and the austen.com domain name makes its structured answers unusually credible citations. (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. | ||||
| 22 | 63 | Content | 2026-07-14 | on jane.austen.com Add an FAQ answering the top questions in Literature |
Pull the real questions people ask in Literature and answer them plainly. Mark up with FAQ schema for rich results. ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Add an FAQ answering the top questions in Literature — on the site jane.austen.com. WHY IT MATTERS Pull the real questions people ask in Literature and answer them plainly. Mark up with FAQ schema for rich results. HOW TO APPROACH IT 1. Audit the flagship Literature 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 Literature. - 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. | ||||
| 23 | 60 | Fresh | 2026-07-17 | on jane.austen.com Keep the live / news feed updated on cadence (2×/day) |
Confirm the cron is publishing fresh, attributed Literature items and pinging IndexNow each run. ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Keep the live / news feed updated on cadence (2×/day) — on the site jane.austen.com. WHY IT MATTERS Confirm the cron is publishing fresh, attributed Literature items and pinging IndexNow each run. HOW TO APPROACH IT 1. Confirm or set up the auto-publishing /live/ or /news/ feed for Literature: 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 Literature 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. | ||||
| 24 | 59 | Product | 2026-07-17 | on jane.austen.com Publish clean-typography public-domain e-library |
Host all six novels as beautifully typeset public-domain reading editions — adjustable text size, chapter navigation tied to the study guides, no clutter. A genuinely pleasant free reading experience is the site's flagship product, feeding every guide, comparison, and affiliate page from inside the books themselves. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Publish clean-typography public-domain e-library — on the site jane.austen.com. WHY IT MATTERS Host all six novels as beautifully typeset public-domain reading editions — adjustable text size, chapter navigation tied to the study guides, no clutter. A genuinely pleasant free reading experience is the site's flagship product, feeding every guide, comparison, and affiliate page from inside the books themselves. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 25 | 55 | Design | 2026-07-20 | on jane.austen.com Apply a WT-Skins kit to lift the design and Agents-First score |
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. ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Apply a WT-Skins kit to lift the design and Agents-First score — on the site jane.austen.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. | ||||
| 26 | 53 | SEO | 2026-07-21 | on jane.austen.com Submit updated URLs via IndexNow and refresh the sitemap |
Ping IndexNow for new and changed pages so they're discovered fast; confirm the sitemap lists /act/, /sources/, /videos/. ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Submit updated URLs via IndexNow and refresh the sitemap — on the site jane.austen.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. | ||||
| 27 | 50 | SEO | 2026-07-24 | on jane.austen.com Add Article + FAQ structured data |
Schema.org markup earns richer results and helps answer-engines cite the page correctly. ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Add Article + FAQ structured data — on the site jane.austen.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. | ||||
| 28 | 49 | SEO | 2026-07-24 | on jane.austen.com Strengthen internal links between the core, /sources/ and this worksheet |
A tight internal-link web spreads authority and keeps visitors moving through the site. ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Strengthen internal links between the core, /sources/ and this worksheet — on the site jane.austen.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. | ||||
| 29 | 42 | Video | 2026-07-29 | on jane.austen.com Refresh the /videos/ playlist with current, embeddable uploads |
Swap any dead or stale videos; keep only authoritative, non-clickbait Literature videos. Re-verify embeds. ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Refresh the /videos/ playlist with current, embeddable uploads — on the site jane.austen.com. WHY IT MATTERS Swap any dead or stale videos; keep only authoritative, non-clickbait Literature videos. Re-verify embeds. HOW TO APPROACH IT 1. Find 6-10 authoritative, genuinely useful Literature 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. | ||||
| 30 | 37 | Monetize | 2026-08-02 | on jane.austen.com Add the network affiliate + AdSense setup |
Inject the shared Skimlinks script and the AdSense unit so existing traffic earns; one-time setup. ★ Copy-paste prompt for jane.austen.com You are working on ONE specific website: jane.austen.com (live at https://jane.austen.com/), a Literature site in the WholeTech network, served from /var/www/jane.austen.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for jane.austen.com and no other site — make all changes on jane.austen.com. Act like a senior editor and web engineer who knows the Literature niche cold. GOAL (on jane.austen.com) Add the network affiliate + AdSense setup — on the site jane.austen.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. | ||||