A prioritized, living to-do list for neighborhell.com, built from this site's sources and current trends in Property Rights. 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 neighborhell.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 neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) Lock down sensitive data — nothing private is publicly reachable — on the site neighborhell.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. | ||||
| 2 | 98 | Flagship | 2026-06-20 | on neighborhell.com Build the definitive Property Rights cornerstone guide |
Create the single most useful, authoritative page on Property Rights 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 neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) Build the definitive Property Rights cornerstone guide — on the site neighborhell.com. WHY IT MATTERS Create the single most useful, authoritative page on Property Rights 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 Property Rights — 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 Property Rights 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 neighborhell.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 neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site neighborhell.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. | ||||
| 4 | 97 | Flagship | 2026-06-21 | on neighborhell.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 neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) Make the homepage genuinely distinctive — kill any generic-template feel — on the site neighborhell.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 Property Rights — 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 Property Rights 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. | ||||
| 5 | 96 | Security | 2026-06-21 | on neighborhell.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 neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) Verify HTTPS, security headers & a safe Agents-First surface — on the site neighborhell.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. | ||||
| 6 | 93 | Flagship | 2026-06-23 | on neighborhell.com Add an interactive tool and an email capture for Property Rights |
Build one genuinely useful interactive element for Property Rights (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 neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) Add an interactive tool and an email capture for Property Rights — on the site neighborhell.com. WHY IT MATTERS Build one genuinely useful interactive element for Property Rights (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 Property Rights — 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 Property Rights 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 | 93 | Trends | 2026-06-23 | on neighborhell.com Publish: A current, data-backed explainer in Property Rights |
Trending angle in Property Rights. 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 neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) Publish: A current, data-backed explainer in Property Rights — on the site neighborhell.com. WHY IT MATTERS Trending angle in Property Rights. 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 Property Rights 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 | 85 | Popularity | 2026-06-29 | on neighborhell.com State-by-state fence, tree, and noise law library |
Build the definitive layperson library: one page per state for fence law, overhanging-tree rights, and noise ordinances, sourced to actual statutes with plain-language summaries and last-reviewed dates. Neighbor-dispute searches are urgent, local, and long-tail — fifty accurate state pages beat one viral rant. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) State-by-state fence, tree, and noise law library — on the site neighborhell.com. WHY IT MATTERS Build the definitive layperson library: one page per state for fence law, overhanging-tree rights, and noise ordinances, sourced to actual statutes with plain-language summaries and last-reviewed dates. Neighbor-dispute searches are urgent, local, and long-tail — fifty accurate state pages beat one viral rant. (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 neighborhell.com Publish: The question your Property Rights audience is searching most right now |
Trending angle in Property Rights. 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 neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) Publish: The question your Property Rights audience is searching most right now — on the site neighborhell.com. WHY IT MATTERS Trending angle in Property Rights. 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 Property Rights 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 | 83 | Trends | 2026-06-30 | on neighborhell.com Publish: A 'what changed in 2026' round-up for Property Rights |
Trending angle in Property Rights. 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 neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) Publish: A 'what changed in 2026' round-up for Property Rights — on the site neighborhell.com. WHY IT MATTERS Trending angle in Property Rights. 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 Property Rights 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 | 82 | Popularity | 2026-07-01 | on neighborhell.com Moderated reader-story submissions as shareable content |
Add a submission form for anonymized neighbor-dispute stories that writes a Gmail draft for Paul's moderation — never auto-publishing or auto-sending. Curated true stories with the identifying details scrubbed are this niche's most shareable format and cost nothing but review time. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) Moderated reader-story submissions as shareable content — on the site neighborhell.com. WHY IT MATTERS Add a submission form for anonymized neighbor-dispute stories that writes a Gmail draft for Paul's moderation — never auto-publishing or auto-sending. Curated true stories with the identifying details scrubbed are this niche's most shareable format and cost nothing but review time. (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 neighborhell.com HOA survival guide content cluster |
Publish a guide cluster on HOA conflict — reading CC&Rs, fine dispute procedures, board-meeting rights, when boards overreach — sourced to state HOA statutes. HOA grievance searches spike year-round, carry intense engagement, and naturally interlink with the state-law library. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) HOA survival guide content cluster — on the site neighborhell.com. WHY IT MATTERS Publish a guide cluster on HOA conflict — reading CC&Rs, fine dispute procedures, board-meeting rights, when boards overreach — sourced to state HOA statutes. HOA grievance searches spike year-round, carry intense engagement, and naturally interlink with the state-law library. (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 | 80 | Revenue | 2026-07-03 | on neighborhell.com Amazon documentation-gear recommendations |
Tag the tools disputants genuinely need with colinfirthfan-20 — security cameras, decibel meter apps' hardware companions, property-line survey markers, no-trespassing signage — inside the guides that explain when and how to use each lawfully. Evidence-gathering gear is this audience's honest purchase intent. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) Amazon documentation-gear recommendations — on the site neighborhell.com. WHY IT MATTERS Tag the tools disputants genuinely need with colinfirthfan-20 — security cameras, decibel meter apps' hardware companions, property-line survey markers, no-trespassing signage — inside the guides that explain when and how to use each lawfully. Evidence-gathering gear is this audience's honest purchase intent. (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 | 79 | Revenue | 2026-07-03 | on neighborhell.com AdSense across the state-law library |
Run pub-7759195213529699 throughout the statute-explainer pages, where legal-adjacent informational traffic sustains strong RPMs, while keeping the story-submission flow ad-free. Fifty state pages times three topics is a durable monetized surface that grows with each statute update. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) AdSense across the state-law library — on the site neighborhell.com. WHY IT MATTERS Run pub-7759195213529699 throughout the statute-explainer pages, where legal-adjacent informational traffic sustains strong RPMs, while keeping the story-submission flow ad-free. Fifty state pages times three topics is a durable monetized surface that grows with each statute update. (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. | ||||
| 15 | 74 | Content | 2026-07-07 | on neighborhell.com Deepen the main Property Rights 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 neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) Deepen the main Property Rights guide with current data and examples — on the site neighborhell.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 Property Rights 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 Property Rights. - 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. | ||||
| 16 | 74 | Revenue | 2026-07-07 | on neighborhell.com Boundary-lines newsletter for ongoing disputes |
Mount the wholetech newsletter widget offering a monthly digest of notable neighbor-law rulings and new reader stories, draft-only notifications. Disputes run for months or years; subscribers mid-conflict return repeatedly, compounding both traffic and the story-submission pipeline. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) Boundary-lines newsletter for ongoing disputes — on the site neighborhell.com. WHY IT MATTERS Mount the wholetech newsletter widget offering a monthly digest of notable neighbor-law rulings and new reader stories, draft-only notifications. Disputes run for months or years; subscribers mid-conflict return repeatedly, compounding both traffic and the story-submission pipeline. (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 | 69 | Design | 2026-07-10 | on neighborhell.com Case-file and property-stake visual language |
Art-direct to the dispute's physical world: manila case-file folder panels for stories, surveyor-stake and string-line dividers between sections, chain-link texture in headers, and a restrained caution-yellow accent reserved for warnings. It should feel like a well-organized evidence binder, not a rage blog. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) Case-file and property-stake visual language — on the site neighborhell.com. WHY IT MATTERS Art-direct to the dispute's physical world: manila case-file folder panels for stories, surveyor-stake and string-line dividers between sections, chain-link texture in headers, and a restrained caution-yellow accent reserved for warnings. It should feel like a well-organized evidence binder, not a rage blog. (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 | 69 | Design | 2026-07-10 | on neighborhell.com State-law pages as legal-pad briefs |
Set each statute explainer on a yellow legal-pad motif — ruled lines, red margin rule, typewriter-adjacent serif for citations, stamped 'reviewed' date — so the plain-language summary visually reads as a lawyer's working brief. The format signals diligence on pages where accuracy is the product. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) State-law pages as legal-pad briefs — on the site neighborhell.com. WHY IT MATTERS Set each statute explainer on a yellow legal-pad motif — ruled lines, red margin rule, typewriter-adjacent serif for citations, stamped 'reviewed' date — so the plain-language summary visually reads as a lawyer's working brief. The format signals diligence on pages where accuracy is the product. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point. 2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer. 3. Verify on the live render, not on a file:// preview. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 19 | 67 | AEO | 2026-07-12 | on neighborhell.com FAQ schema on classic boundary questions |
Mark up precise answers — can my neighbor build on the property line, who pays for a shared fence, what counts as a noise violation — with FAQPage schema per state where law differs, then run af-deploy.py above 90. Answer engines field these daily with sloppy sourcing. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) FAQ schema on classic boundary questions — on the site neighborhell.com. WHY IT MATTERS Mark up precise answers — can my neighbor build on the property line, who pays for a shared fence, what counts as a noise violation — with FAQPage schema per state where law differs, then run af-deploy.py above 90. Answer engines field these daily with sloppy sourcing. (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. | ||||
| 20 | 64 | Content | 2026-07-14 | on neighborhell.com Add an FAQ answering the top questions in Property Rights |
Pull the real questions people ask in Property Rights and answer them plainly. Mark up with FAQ schema for rich results. ★ Copy-paste prompt for neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) Add an FAQ answering the top questions in Property Rights — on the site neighborhell.com. WHY IT MATTERS Pull the real questions people ask in Property Rights and answer them plainly. Mark up with FAQ schema for rich results. HOW TO APPROACH IT 1. Audit the flagship Property Rights 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 Property Rights. - 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. | ||||
| 21 | 62 | Product | 2026-07-15 | on neighborhell.com Printable dispute-documentation log template |
Offer a free printable incident log — date, time, description, witnesses, photo reference — matching what mediators and small-claims courts actually want to see, with a companion how-to-document guide. A genuinely useful evidence diary earns links from mediation and legal-aid sites. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) Printable dispute-documentation log template — on the site neighborhell.com. WHY IT MATTERS Offer a free printable incident log — date, time, description, witnesses, photo reference — matching what mediators and small-claims courts actually want to see, with a companion how-to-document guide. A genuinely useful evidence diary earns links from mediation and legal-aid sites. (Fable enhanced action — also on the global worksheet.) HOW TO APPROACH IT 1. Plan the cleanest way to accomplish this, then execute it well. 2. Use real, current information and match the existing quality of the site. CONSTRAINTS - Match the site's existing design, fonts, layout and voice — never a generic AI-template look. - Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units. - Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources. - Reuse the site's existing Google Analytics and AdSense. WHAT "DONE" LOOKS LIKE - The task is fully done, accurate, and live. - Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed. Think through the best approach first, then complete the whole task autonomously before stopping. | ||||
| 22 | 57 | Fresh | 2026-07-19 | on neighborhell.com Keep the live / news feed updated on cadence (2×/day) |
Confirm the cron is publishing fresh, attributed Property Rights items and pinging IndexNow each run. ★ Copy-paste prompt for neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) Keep the live / news feed updated on cadence (2×/day) — on the site neighborhell.com. WHY IT MATTERS Confirm the cron is publishing fresh, attributed Property Rights items and pinging IndexNow each run. HOW TO APPROACH IT 1. Confirm or set up the auto-publishing /live/ or /news/ feed for Property Rights: 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 Property Rights 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. | ||||
| 23 | 55 | Design | 2026-07-20 | on neighborhell.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 neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) Apply a WT-Skins kit to lift the design and Agents-First score — on the site neighborhell.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. | ||||
| 24 | 55 | SEO | 2026-07-20 | on neighborhell.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 neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) Submit updated URLs via IndexNow and refresh the sitemap — on the site neighborhell.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. | ||||
| 25 | 46 | SEO | 2026-07-26 | on neighborhell.com Add Article + FAQ structured data |
Schema.org markup earns richer results and helps answer-engines cite the page correctly. ★ Copy-paste prompt for neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) Add Article + FAQ structured data — on the site neighborhell.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. | ||||
| 26 | 45 | SEO | 2026-07-27 | on neighborhell.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 neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) Strengthen internal links between the core, /sources/ and this worksheet — on the site neighborhell.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. | ||||
| 27 | 43 | Video | 2026-07-28 | on neighborhell.com Refresh the /videos/ playlist with current, embeddable uploads |
Swap any dead or stale videos; keep only authoritative, non-clickbait Property Rights videos. Re-verify embeds. ★ Copy-paste prompt for neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) Refresh the /videos/ playlist with current, embeddable uploads — on the site neighborhell.com. WHY IT MATTERS Swap any dead or stale videos; keep only authoritative, non-clickbait Property Rights videos. Re-verify embeds. HOW TO APPROACH IT 1. Find 6-10 authoritative, genuinely useful Property Rights 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. | ||||
| 28 | 40 | Monetize | 2026-07-31 | on neighborhell.com Verify affiliate links and ad placement resolve correctly |
Spot-check Skimlinks / Amazon links and AdSense units; remove anything broken or low-value. ★ Copy-paste prompt for neighborhell.com You are working on ONE specific website: neighborhell.com (live at https://neighborhell.com/), a Property Rights site in the WholeTech network, served from /var/www/neighborhell.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for neighborhell.com and no other site — make all changes on neighborhell.com. Act like a senior editor and web engineer who knows the Property Rights niche cold. GOAL (on neighborhell.com) Verify affiliate links and ad placement resolve correctly — on the site neighborhell.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. | ||||