What to do next on this site

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

GOAL (on bmicrophone.com)
Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site bmicrophone.com.

WHY IT MATTERS
Assume a determined automated, AI-driven attacker. Enforce HTTPS, add a sensible Content-Security-Policy plus the standard security headers, eliminate open redirects and reflected user input, validate and rate-limit any form, and ensure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data — never internal or personal information.

HOW TO APPROACH IT
1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200.
2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public.
3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy).
4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A logged-out request to every sensitive path returns 403/404 — verified, not assumed.
- No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON.
- HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Lock down sensitive data — nothing private is publicly reachable — on the site bmicrophone.com.

WHY IT MATTERS
Make sure a logged-out visitor or bot cannot reach anything sensitive on this site: /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404, never 200. Then scan the served HTML, JS, and JSON for leaked keys, tokens, internal emails, or personal data and remove them.

HOW TO APPROACH IT
1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200.
2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public.
3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy).
4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A logged-out request to every sensitive path returns 403/404 — verified, not assumed.
- No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON.
- HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Verify HTTPS, security headers & a safe Agents-First surface — on the site bmicrophone.com.

WHY IT MATTERS
Confirm the certificate is valid and HTTPS is forced, the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, CSP), and the Agents-First endpoints expose only public, non-sensitive information — trustworthy to humans and safe for the agents reading it.

HOW TO APPROACH IT
1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200.
2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public.
3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy).
4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A logged-out request to every sensitive path returns 403/404 — verified, not assumed.
- No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON.
- HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Build the definitive Audio & Video Production cornerstone guide — on the site bmicrophone.com.

WHY IT MATTERS
Create the single most useful, authoritative page on Audio & Video Production 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 Audio & Video Production — 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 Audio & Video Production resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Make the homepage genuinely distinctive — kill any generic-template feel — on the site bmicrophone.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 Audio & Video Production — 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 Audio & Video Production resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Add an interactive tool and an email capture for Audio & Video Production — on the site bmicrophone.com.

WHY IT MATTERS
Build one genuinely useful interactive element for Audio & Video Production (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 Audio & Video Production — 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 Audio & Video Production resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Publish: AI editing and transcription in the production pipeline — on the site bmicrophone.com.

WHY IT MATTERS
Trending angle in Audio & Video Production. 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 Audio & Video Production reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Publish: The gear and codecs worth upgrading to now — on the site bmicrophone.com.

WHY IT MATTERS
Trending angle in Audio & Video Production. 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 Audio & Video Production reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Head-to-head mic comparison pages with spec tables — on the site bmicrophone.com.

WHY IT MATTERS
Publish direct comparisons — SM7B versus MV7, PodMic versus Q2U, NT1 versus AT2020 — with honest spec tables (pattern, output level, connector, price tier) from manufacturer datasheets. Versus queries are how mic buyers actually search, and clean spec-table pages win them from thin listicle competitors. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Curated mic shootout videos on /videos/ — on the site bmicrophone.com.

WHY IT MATTERS
Build the /videos/ page from reputable published mic shootouts and technique breakdowns, verifying every embed with check-embed.mjs and dropping failures per the embeddable-only rule. Hearing capsule differences is the decision moment for mic buyers; a curated listening shelf makes this site the comparison destination. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Which-mic-for-X decision guides by use case — on the site bmicrophone.com.

WHY IT MATTERS
Write one decision guide per use case — podcasting, vocals, streaming, field recording, untreated rooms — each ending in two or three concrete picks with reasoning about pattern and room forgiveness. Use-case guides catch buyers a step before the versus search and route them into the comparison 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.

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

GOAL (on bmicrophone.com)
Publish: Livestream setups that punch above their cost — on the site bmicrophone.com.

WHY IT MATTERS
Trending angle in Audio & Video Production. 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 Audio & Video Production reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Publish: Color / audio workflows pros are adopting — on the site bmicrophone.com.

WHY IT MATTERS
Trending angle in Audio & Video Production. 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 Audio & Video Production reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Check Impact catalog for audio retailer brands — on the site bmicrophone.com.

WHY IT MATTERS
Review the Impact account's approved-brands worksheet for music-gear retailers and add disclosed retailer links alongside Amazon where a legitimate program exists, giving readers a price-comparison choice. Only brands actually present in the account — no invented partnerships, and Amazon remains the fallback everywhere else. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Amazon links on every mic mentioned sitewide — on the site bmicrophone.com.

WHY IT MATTERS
Tag every microphone, boom arm, and interface referenced across comparisons and guides with colinfirthfan-20 links, with plain affiliate disclosure. Mic content is bottom-of-funnel by nature — readers arrive ready to purchase — making Associates the site's natural primary revenue with zero editorial compromise required. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
AdSense on technique and education articles — on the site bmicrophone.com.

WHY IT MATTERS
Run pub-7759195213529699 on mic-technique and recording-education articles — proximity effect, gain staging, pop-filter placement — while keeping comparison pages ad-light so affiliate links face no competition. Educational search traffic monetizes via display; buyer-intent pages monetize via Associates; the two layers shouldn't cannibalize. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Deepen the main Audio & Video Production guide with current data and examples — on the site bmicrophone.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 Audio & Video Production 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 Audio & Video Production.
- No filler and no fabricated specifics — every number is current and sourced.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Build /sources/ out to at least 10 authoritative links — on the site bmicrophone.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 Audio & Video Production.
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 Audio & Video Production expert would trust.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Add an FAQ answering the top questions in Audio & Video Production — on the site bmicrophone.com.

WHY IT MATTERS
Pull the real questions people ask in Audio & Video Production and answer them plainly. Mark up with FAQ schema for rich results.

HOW TO APPROACH IT
1. Audit the flagship Audio & Video Production 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 Audio & Video Production.
- No filler and no fabricated specifics — every number is current and sourced.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Matte-black studio aesthetic with polar-pattern icons — on the site bmicrophone.com.

WHY IT MATTERS
Art-direct in the material language of the gear: matte-black surfaces, brass grille-mesh textures, and polar-pattern diagrams (cardioid, figure-8, omni) used as the site's section iconography. Spec callouts styled like frequency-response charts make the pages feel like datasheets audio people already trust. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point.
2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer.
3. Verify on the live render, not on a file:// preview.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Comparison tables styled as patch-bay rows — on the site bmicrophone.com.

WHY IT MATTERS
Style comparison tables as studio patch-bay strips — labeled channel rows, jack-point column markers, cable-trace lines connecting a mic to its recommended interface and arm. It turns dry spec grids into signal-chain diagrams, which is exactly how recording people mentally model gear decisions. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point.
2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer.
3. Verify on the live render, not on a file:// preview.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Product and FAQ schema on documented artist rigs — on the site bmicrophone.com.

WHY IT MATTERS
Add Product schema to every reviewed mic and FAQPage blocks answering 'what mic does Joe Rogan use' style queries — strictly from publicly documented rigs, never speculation. Run af-deploy.py to 90+; rig questions are massive answer-engine volume and reward the site that answers them with sources. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Three-question mic-picker wizard tool — on the site bmicrophone.com.

WHY IT MATTERS
Ship a static-JS picker — use case, budget, treated or untreated room — outputting one primary recommendation plus one alternative, each linking its comparison page and tagged purchase link. It compresses the site's entire editorial judgment into thirty seconds and becomes the page people send friends. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

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

WHY IT MATTERS
Confirm the cron is publishing fresh, attributed Audio & Video Production items and pinging IndexNow each run.

HOW TO APPROACH IT
1. Confirm or set up the auto-publishing /live/ or /news/ feed for Audio & Video Production: 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 Audio & Video Production items on schedule and is discovered quickly.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Apply a WT-Skins kit to lift the design and Agents-First score — on the site bmicrophone.com.

WHY IT MATTERS
The page looks generic without a kit. Roll the cluster's kit (snapshot the old design first) to get the AF score into the 90s.

HOW TO APPROACH IT
1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point.
2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer.
3. Verify on the live render, not on a file:// preview.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Submit updated URLs via IndexNow and refresh the sitemap — on the site bmicrophone.com.

WHY IT MATTERS
Ping IndexNow for new and changed pages so they're discovered fast; confirm the sitemap lists /act/, /sources/, /videos/.

HOW TO APPROACH IT
1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely.
2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The change validates cleanly and the affected pages are eligible for richer results or faster discovery.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Add Article + FAQ structured data — on the site bmicrophone.com.

WHY IT MATTERS
Schema.org markup earns richer results and helps answer-engines cite the page correctly.

HOW TO APPROACH IT
1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely.
2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The change validates cleanly and the affected pages are eligible for richer results or faster discovery.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Strengthen internal links between the core, /sources/ and this worksheet — on the site bmicrophone.com.

WHY IT MATTERS
A tight internal-link web spreads authority and keeps visitors moving through the site.

HOW TO APPROACH IT
1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely.
2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The change validates cleanly and the affected pages are eligible for richer results or faster discovery.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

GOAL (on bmicrophone.com)
Add the network affiliate + AdSense setup — on the site bmicrophone.com.

WHY IT MATTERS
Inject the shared Skimlinks script and the AdSense unit so existing traffic earns; one-time setup.

HOW TO APPROACH IT
1. Make the change — verify affiliate links resolve, or add the shared affiliate + AdSense setup.
2. Keep commerce low-key and well-integrated: subtle in-content links, not a bolted-on banner block.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Links resolve and can earn, and placement is tasteful and does not hurt the reading experience.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

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

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

WHY IT MATTERS
Swap any dead or stale videos; keep only authoritative, non-clickbait Audio & Video Production videos. Re-verify embeds.

HOW TO APPROACH IT
1. Find 6-10 authoritative, genuinely useful Audio & Video Production 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.