Survival skills, bushcraft techniques, emergency preparedness, wilderness first aid, and building self-reliance for any situation.
Specific implementation depends on current site state — audit before acting.
Specific implementation depends on current site state — audit before acting.
Specific implementation depends on current site state — audit before acting.
Specific implementation depends on current site state — audit before acting.
Page should load fast and read clean on a phone first. Audit current mobile UX before adding features.
Every page should have ONE primary call-to-action visible above the fold. Most network sites scatter intent — this site likely does too.
Add JSON-LD for the appropriate primary entity type (LocalBusiness, Article, RealEstateListing, etc.).
Who runs this, why it exists, what readers get. Builds trust.
8-10 most-common questions with direct answers. Captures voice-search and AI-citation traffic.
Consistent footer linking to 4-6 sister properties on the WholeTech network.
Universal SEO prompts following the Opus 4.7 framework at claude.wholetech.com/prompting/. Replace bracketed placeholders.
<context> This site is [SITE]. Its current scope is described at the top of the site's index page. The single biggest content gap is a missing pillar page on [TOPIC]. </context> <instructions> Write a 2,500-word pillar page on [TOPIC] for this site. Lead with the strongest claim. Use 6 H2 sections covering different facets. Cite at least one external source per section. Cross-link to relevant network properties at https://wholetech.com. </instructions> <constraints> - No preamble. No "in today's rapidly evolving" opener. - Year-anchor any title. - Single H1, six H2s, short conclusion. - Voice: match the site's existing tone. </constraints>
<context> Audit the JSON-LD on [SITE]. Likely state: WebSite + Organization only. </context> <instructions> Identify the main entity type the site should use (Article / TVSeries / RealEstateListing / LocalBusiness / etc.) and generate the JSON-LD block to add to the head of every relevant page. </instructions>
<context> The site ranks for [PRIMARY KEYWORD] but is missing long-tail variations. </context> <instructions> Generate 20 long-tail keyword variations for [PRIMARY KEYWORD] grouped into 4 intent clusters (informational, comparison, transactional, navigational). For each cluster, propose one specific page title that targets it. </instructions>
<context> Topic: [TOPIC]. Audience: [AUDIENCE]. Site voice: [match site]. </context> <instructions> Write a 800-word article. Lead with the strongest claim. Three H2 sections. Cite 2 external sources. Close with a single recommended next action for the reader. </instructions> <constraints> - No preamble. No hedging. - Match the site's editorial voice. - One pull-quote, set off in the body. </constraints>
<context> The round-up is [N] [things] for [audience]. Current best practice on this topic: [paste current top result]. </context> <instructions> Write the round-up. Each item: H3 title, 80-120 word section, one specific example, one external link. Open with a 150-word lede that explains the inclusion criteria. Close with what the list deliberately omits. </instructions>
Before pouring effort in, decide explicitly: is this site worth growing, holding at current state, or sunsetting in favor of a higher-leverage property?
Network sites compound when they cross-link. If this site won't link to 3-5 sister properties, ask why it's in the network.
Bot traffic isn't demand. Confirm real human traffic exists before scaling content production on this property.