Landing page and web copy
Skill the-nam-shub/e5-real-skills/skills/landing-page-and-web-copy
Guidance for writing, structuring, and optimizing B2B landing page and website copy — trigger when a user needs help with homepage messaging, hero sections, CTAs, product pages, or conversion copy.From its SKILL.md
npx -y skills add the-nam-shub/e5-real-skills --skill landing-page-and-web-copyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
26.1 KB, ~5.6k tokens by cl100k_base, as published. Nobody here has run it
Landing Page and Web Copy
Overview
This skill covers best practices for writing and structuring B2B landing page and website copy, including hero sections, headlines, CTAs, product pages, feature descriptions, and page-level information hierarchy. All practices are sourced exclusively from Exit Five podcast guests across 13 episodes. Do not supplement with general copywriting knowledge not represented here.
Hero Section and Above-the-Fold Copy
Communicate problem, solution, and outcome within three seconds. The hero section has approximately three seconds to convince a visitor your product is relevant to them. Use this space to communicate the specific pain you solve and the result they'll get — not features, technology, or integrations. The hero should create an "aha moment" that makes visitors want to continue reading. (Source: Talia Wolf, Episode #132)
Limit hero headlines to three lines maximum. Keep headlines concise and scannable. Longer headlines take up excessive space, feel overwhelming, and are less likely to be read. A shorter, more focused headline conveys the value proposition more effectively. (Source: Gabby Sellam, Episode #218)
Focus the hero on a single primary service or benefit. If your company offers multiple services, do not list them all above the fold. Choose one primary service or benefit to highlight. Additional offerings can be explained lower on the page. This reduces cognitive load and keeps the hero focused on a single conversion goal. (Source: Gabby Sellam, Episode #218)
Do not overload the hero with multiple value propositions, features, or CTAs. Limit the amount of content visible above the fold. Complexity can be introduced lower on the page for those who scroll. (Source: Gabby Sellam, Episode #218)
Align landing page header copy to the entry point that drove traffic. Ensure continuity between the copy in the traffic source (ad, email, etc.) and the main headline on the landing page. The landing page header should reinforce and extend that message rather than introduce a new one, reducing cognitive friction. (Source: Gabby Sellam, Episode #218)
Add a problem block immediately below the hero section. Place a "problem block" directly under your hero that empathizes with the prospect's pain points. List 3–5 specific problems your audience faces (e.g., "Manual calendar scheduling takes 3–7 emails back and forth"). This mirrors the prospect's situation back to them, builds rapport, and signals that the page is about solving their problems, not promoting your company. (Source: Tas Bober, Episode #185)
Headlines and Subheadings
Avoid vague, generic hero headlines that could apply to any product. Headlines like "Unlock Insights, Drive Revenue" or "Streamline Your Deliveries" fail to communicate what the product does or who it's for. A strong hero headline should clearly state what the product does and ideally hint at who it's for. Avoid marketing jargon and feature lists in the hero. (Source: Guy Yalif, Episode #251)
Ensure headlines and subheadings answer four key questions. Use the "rule of four" framework to evaluate homepage hero messaging. The headline and subheading combination should clearly communicate: (1) what the product/service does, (2) who it's for, (3) why the user should care (the benefit or outcome), and (4) trust indicators. If any of these are missing, the messaging is incomplete. (Source: Diane Wiredu, Episode #220)
Use audience-specific headlines to qualify visitors immediately. Write your homepage headline to explicitly name your target audience (e.g., "For HubSpot Super Admins" or "For Engineering Firms"). This allows visitors to instantly know if the product is for them. Visitors who don't match will leave quickly; those who do will stay engaged. This is more effective than generic or clever headlines. (Source: Dave Gerhardt, Episode #178)
Use industry-specific language and terminology in headlines. Avoid generic benefit statements (e.g., "Maximize efficiency and lower cost") that could apply to any industry. Use specific language that resonates with your target audience (e.g., "Assess any risk. No field visit required" for utility companies). This signals the page was built for them. (Source: Will Hoekenga, Episode #218)
Replace placeholder headlines with specific, audience-focused language. Placeholder headlines are generic statements that could apply to any industry or product (e.g., "Answer any question"). Replace them with specific language that speaks directly to your target audience's actual needs and context. (Source: Will Hoekenga, Episode #218)
Avoid yes/no questions in headlines and subheadings. Questions in copy should not be answerable with a simple yes or no — if the reader answers "no," they disengage. Use open-ended questions that prompt reflection or curiosity (e.g., "How many times have you..." instead of "Do you want..."). (Source: Diane Wiredu, Episode #220)
Use benefit-driven section headers instead of generic labels. Replace generic section headers ("Key Features," "Delivery Success," "User Benefits") with headers that speak to customer outcomes and pain points. For example, instead of "Key Features," use "Plan Less, Deliver More" or "Reduce Planning Time by 40%." (Source: Scott Cappuzzo, Episode #251)
Use clear, specific headers that help skimmers quickly find information. Recognize that most visitors skim product pages. Use headers that are specific and informative (e.g., "Detect outages quickly" instead of "Advanced monitoring"). Headers should help prospects quickly locate the argument or feature they're looking for. (Source: Robert Kaminski, Episode #222)
Value Propositions and Body Copy
Clearly identify what your product is in the headline or early subheading. Users should understand what you sell within the first few lines of the page. Do not bury product identification in paragraphs or require users to scroll to understand what you offer. State clearly what the product is (e.g., "Metal 3D Printers for Medical Implants"), then expand on benefits and features below. (Source: Tas Bober, Episode #218)
Structure the homepage with category definition, value proposition, and differentiation. Lead with category definition (what is it?) so visitors immediately understand what you do. Follow with a value proposition that communicates your "onliness" (why you, not competitors). Then provide proof and differentiation. This answers the questions buyers ask: What is it? Is it for me? Why you? (Source: Peep Laja, Episode #119)
Rewrite USPs and value propositions to focus on user outcomes, not company features. When listing key value propositions on the homepage, avoid company-centric language like "we've built" or feature-focused statements. Translate each USP into what the user gains or can do. Ask "so what?" for each claim to ensure it answers "what's in it for me?" (Source: Lee Reshef, Episode #220)
Apply the "so what" test to every line of homepage copy. For every line of copy, ask "so what?" to identify whether you're describing a feature or translating it into a benefit for the user. Replace company-centric language ("we built," "we've packaged") with user-focused language ("you can," "you'll get"). (Source: Diane Wiredu, Episode #220)
Replace generic benefit statements with specific, measurable outcomes from customer results. Avoid vague claims like "Maximize efficiency and lower cost." Instead, use specific, quantified results from actual customers (e.g., "Eliminated 300 hours of inspection time"). Specific outcomes are more credible and persuasive than generic benefits. (Source: Tas Bober, Episode #218)
Avoid placeholder copy formulas without pushing further. Formulas like "Product X for Persona Y" are starting points, not finished copy. They should only appear on the page if both the product category and persona are extremely clear and specific. Otherwise, push beyond the formula to create messaging that actually resonates and builds curiosity. Avoid vague qualifiers like "modern" or "people-centric" that don't differentiate. (Source: Diane Wiredu, Episode #220)
Write landing pages from the buyer's perspective, not the seller's. Structure landing page content to answer the questions a buyer actually needs answered before engaging: What problem does this solve? What's the biggest thing it enables me to do? What's the starting price? What happens after I submit my information? Avoid jargon, generic ROI claims, and gatekeeping basic product information. (Source: Tas Bober, Episode #154)
Use customer search language, not internal product names, in content. Optimize page titles, headings, and content using the language and keywords that customers actually search for, not internal product or feature names. For example, use "GDPR compliance" instead of "consent management," or "charge rent online" instead of a product name. (Source: Ross Simmonds, Episode #224)
Edit homepage copy ruthlessly and use whitespace to support messaging hierarchy. More copy is not inherently bad, but it must be edited for clarity and necessity. Prioritize which key messages are essential and remove redundancy. Use whitespace and design to break up copy and guide the reader's eye to the most important elements. Supporting visuals should enhance, not duplicate, the copy. (Source: Diane Wiredu, Episode #220)
Product Pages
Avoid excessive copy on product pages; prioritize clarity and scanability. Product pages with excessive text overwhelm visitors and reduce engagement. Prioritize concise, scannable copy that gets to the point quickly. Use headers, bullet points, and visual breaks to make content digestible. (Source: Robert Kaminski, Episode #222)
Do not repeat the same feature list multiple times on a product page. Avoid listing the same features or capabilities in multiple sections. If you introduce features in one section, do not repeat that same list later on the page. This creates redundancy and wastes space that could be used for deeper explanation or differentiation. (Source: Robert Kaminski, Episode #222)
Avoid making unbelievable or disconnected value claims. Do not make value arguments that don't logically connect to the product's core function. For example, claiming that monitoring software "increases workplace productivity" is unbelievable and weakens credibility. Stick to value claims that directly flow from what the product does. (Source: Robert Kaminski, Episode #222)
Bundle features into value stories rather than feature-dumping. Instead of listing all features individually, group related features into thematic blocks that tell a story about what the buyer can accomplish. For example, instead of listing "group scheduling, webinar scheduling, dual hosting," bundle them with context: "As a marketer hosting multi-person events, our group scheduling, webinar functionality, and dual hosting let you manage this without worrying about admin work." Prioritize features by impact: major differentiators get their own block, related features bundle together, and minor features go in FAQs. (Source: Tas Bober, Episode #185)
Identify non-negotiable features through sales and customer conversations. When writing product pages, determine which features are non-negotiable for customers in your buying process. Talk to sales about what customers ask for during evaluation, and ask customers directly what features they must have. Balance emotional/benefit-driven copy with specific feature clarity — as prospects get closer to buying, they need to know "does it have X?" (Source: Will Hoekenga, Episode #181)
Use simple, customer-centric language in feature descriptions. Avoid jargon, acronyms, and clever internal names in feature descriptions. Use language your customers already understand. If a term is something you created internally and requires explanation, spell it out instead. Apply a "jobs to be done" test: if you can look at a feature description and understand the job it's trying to get done, you've achieved good clarity. (Source: Bill Wilson, Episode #216)
Prioritize FAQs as a high-traffic section on landing pages. FAQs are one of the most-clicked sections on landing pages, often accounting for 15–17% of all page clicks. Populate FAQs with: (1) features that can't stand alone as value propositions, (2) common objections from sales and customer calls, and (3) questions generated by asking ChatGPT "what would someone from [persona] ask about [product]?" Limit FAQs to 5–7 questions per page and make them specific to that page's context. Use heat mapping tools to identify which FAQs get the most engagement, then consider promoting high-traffic FAQs to their own sections. (Source: Tas Bober, Episode #185)
CTAs (Calls to Action)
Prioritize clarity over creativity in CTA design and copy. Clarity should be the primary goal. If a CTA is creative but unclear about what happens when clicked, it will underperform. Once clarity is established, you can layer on creative elements to enhance emotional appeal. Never sacrifice clarity for the sake of being novel or visually interesting. (Source: Guy Yalif, Episode #251)
Replace vague CTA language with specific, action-oriented text that sets expectations. Avoid generic CTAs like "Submit" or "Learn more." Use specific language that tells users what will happen (e.g., "Schedule a demo," "Get your free audit," "Book a call"). Specific CTAs reduce friction by clarifying the next step and setting expectations. (Source: Tas Bober, Episode #218)
Ensure CTA wording matches the prospect's actual next step, not just your ideal next step. Choose CTA text that reflects what the prospect actually expects to happen. For example, "Get started today" should lead to an immediate product experience, not a sales call booking form. Mismatched CTAs create friction and reduce conversions. (Source: Robert Kaminski, Episode #222)
Use one consistent CTA throughout the page to reduce decision fatigue. Pick a single CTA label and use it consistently throughout your landing page, even if it appears multiple times. Avoid using different CTA labels (e.g., "Book a Meeting," "Talk to an Expert," "Get a Demo") that all lead to the same destination. Multiple CTA variations create decision fatigue. Test one CTA variation for a couple of weeks, then test a different variation. (Source: Tas Bober, Episode #185)
Personalize CTA copy by using possessive language. Instead of generic CTA copy like "Book Demo," test "Book Your Demo" to make the CTA feel more personally relevant to the visitor. This small linguistic shift makes the action feel more directly applicable to the individual user. (Source: Scott Cappuzzo, Episode #251)
Test CTA copy as a low-friction optimization. Test variations of CTA copy to identify action-oriented language that reduces friction and clearly communicates the outcome. Move beyond generic phrases like "Learn More" or "See This Page" to more specific, benefit-driven language. Small tweaks to CTA copy can have significant impact on conversion rates. (Note: the relative priority of friction reduction vs. motivation-building is contested — see Where Experts Disagree.) (Source: Scott Cappuzzo, Episode #251)
Make CTA outcomes explicit in product section links. When linking to product pages or features from the homepage, use action-oriented language that clarifies what the visitor will see or do. Avoid vague labels like just the product name (e.g., "Conversion Intelligence"). Instead, use language like "Explore Conversion Intelligence" or "See How Conversion Intelligence Works." (Source: Scott Cappuzzo, Episode #251)
Page Structure and Workflow
Write messaging and copy first, then design the page to amplify that message. Establish your core message, value proposition, and CTA copy before beginning the design process. Write out the story you're telling about your customer — where they are, what they're struggling with, what hasn't worked, the solution, and why it matters. Once this narrative is clear, design elements should be chosen to amplify and support that message, not the other way around. (Note: this is contested — see Where Experts Disagree.) (Source: Talia Wolf, Episodes #251 and #231)
Prioritize page structure and information hierarchy before polishing copy. In the hierarchy of web page effectiveness, structure (what information appears where) matters more than copy polish. A well-written headline in the wrong position will underperform even with great copy. Work with design and product marketing to determine what information matters most to customers and in what order it should appear. Place social proof near the claims it supports, not at the bottom of the page by default. (Note: this is contested — see Where Experts Disagree.) (Source: Will Hoekenga, Episode #181)
Prioritize increasing user motivation over reducing friction in conversion optimization. Motivation is 10x more powerful than friction reduction. Users with high motivation will tolerate significant friction (e.g., long forms, gated content) to get what they want. Focus messaging and copy on increasing motivation — making people want to take action — rather than optimizing form fields or removing steps. Motivation is driven by words and messaging, not design. (Note: this is contested — see Where Experts Disagree.) (Source: Peep Laja, Episode #119)
Where Experts Disagree
1. Should you write copy before designing, or prioritize page structure first?
Support summary: 3 vs 1
Position A — Copy first, then design (supported by Talia Wolf and Peep Laja): Write all copy and messaging before any design or wireframing begins. Copy should drive information hierarchy and design decisions. Starting with design leads to copy being treated as decoration rather than strategy.
- Talia Wolf (Episodes #251 and #231) advocates writing the full narrative story about the customer first — where they are, what they're struggling with, what hasn't worked, the solution — then designing to amplify that message. She explicitly recommends reversing the typical workflow: write full copy first, then wireframe around that copy, then design. She argues that starting with design creates a product-centric mentality.
- Peep Laja (Episode #119) states that copy should drive information hierarchy and design decisions, not the reverse. When designers allocate space first, copywriters become decorators rather than strategists.
Position B — Structure first, then polish copy (supported by Will Hoekenga): Page structure and information hierarchy should be prioritized before polishing copy. A well-written headline in the wrong position will underperform even with great copy, so getting the structure right is the prerequisite.
- Will Hoekenga (Episode #181) argues that in the hierarchy of web page effectiveness, structure (what information appears where) matters more than copy polish. He recommends working with design and product marketing to determine information order before writing polished copy.
Context dependency: This disagreement may partially dissolve depending on interpretation. Hoekenga may mean "plan structure before polishing copy" rather than "design before writing." However, the explicit advice conflicts: Wolf and Laja say write copy before wireframing and design, while Hoekenga says structure decisions precede copy polish. This is a genuine disagreement about workflow sequencing.
Why it matters: The workflow order determines whether messaging or visual layout drives the page, which has downstream effects on whether copy serves the customer's decision-making process or fills pre-allocated design boxes.
2. Should conversion optimization focus primarily on increasing motivation or reducing friction?
Support summary: 4 vs 1
Position A — Motivation first (supported by Peep Laja): Motivation is 10x more powerful than friction reduction. Users with high motivation will tolerate significant friction. Focus messaging and copy on making people want to take action rather than optimizing form fields or removing steps.
- Peep Laja (Episode #119) explicitly states motivation is 10x more powerful than friction reduction and that motivated users will tolerate long forms and gated content. He argues motivation is driven by words and messaging, not design, and makes this claim as a general principle rather than a stage-specific one.
Position B — Friction reduction is a meaningful and actionable lever (supported by Gabby Sellam, Robert Kaminski, Scott Cappuzzo, and Tas Bober): Specific friction points like vague CTAs, mismatched expectations, and cognitive overload in the hero section directly reduce conversions and should be actively addressed.
- Gabby Sellam (Episode #218) recommends limiting hero content to reduce cognitive load, keeping headlines to three lines maximum, and avoiding overloading visitors with too much information above the fold — all friction-reduction tactics.
- Robert Kaminski (Episode #222) argues that mismatched CTAs (e.g., "Get started" leading to a demo form) create friction and reduce conversions, and that excessive copy overwhelms visitors. He treats friction reduction as a primary optimization lever.
- Scott Cappuzzo (Episode #251) recommends testing CTA copy as a "low-friction optimization" and using action-oriented language to reduce friction and increase clarity.
- Tas Bober (Episode #185) recommends using a single consistent CTA throughout the page specifically to reduce decision fatigue — a friction-reduction argument — as a primary conversion optimization tactic.
Context dependency: Laja's claim may apply more to top-of-funnel or high-consideration purchases where desire is the bottleneck, while friction reduction may matter more for high-intent, bottom-of-funnel pages where motivation is already present. However, Laja makes the claim as a general principle, making this a genuine disagreement at the level of strategic prioritization.
Trend note: The four friction-reduction advocates all appear in more recent episodes (2025), while Laja's motivation-first argument is from early 2024. This may reflect a field shift toward tactical friction optimization, though the sample is too small to be conclusive.
Why it matters: If Laja is right, B2B marketers are wasting time on CTA copy tests and form optimization when they should be investing in stronger messaging and value propositions. If the friction-reduction camp is right, ignoring tactical page improvements leaves measurable conversion gains on the table.
What NOT To Do
- Do not use generic hero headlines that could apply to any product or company. Specificity about who the product is for and what it does is non-negotiable. (Source: Guy Yalif, Episode #251)
- Do not use yes/no questions in headlines or subheadings. A "no" answer causes the reader to disengage immediately. (Source: Diane Wiredu, Episode #220)
- Do not bury product identification in body copy. Visitors should understand what you sell within the first few lines of the page. (Source: Tas Bober, Episode #218)
- Do not use vague CTAs like "Submit," "Learn More," or "See This Page." These fail to set expectations or communicate what happens next. (Source: Tas Bober, Episode #218; Scott Cappuzzo, Episode #251)
- Do not mismatch CTA language with the actual next step. "Get started today" should not lead to a demo booking form. (Source: Robert Kaminski, Episode #222)
- Do not use multiple different CTA labels on the same page that all lead to the same destination. This creates decision fatigue. (Source: Tas Bober, Episode #185)
- Do not repeat the same feature list multiple times on a product page. (Source: Robert Kaminski, Episode #222)
- Do not make value claims that don't logically connect to what the product actually does. Unbelievable claims damage credibility. (Source: Robert Kaminski, Episode #222)
- Do not use internal product names or jargon in feature descriptions or page headings. Use the language customers actually search for and speak. (Source: Bill Wilson, Episode #216; Ross Simmonds, Episode #224)
- Do not use company-centric language ("we've built," "we've packaged") in USPs and value propositions. Translate everything into user outcomes. (Source: Diane Wiredu, Episode #220; Lee Reshef, Episode #220)
- Do not use vague qualifiers like "modern" or "people-centric" that don't differentiate your product from competitors. (Source: Diane Wiredu, Episode #220)
- Do not design the page first and fit copy into pre-allocated space — this turns copywriters into decorators and produces product-centric, not customer-centric, messaging. (Note: contested — see Where Experts Disagree.) (Source: Talia Wolf, Episodes #251 and #231; Peep Laja, Episode #119)
- Do not introduce a new message on the landing page that doesn't match the ad, email, or link that drove the traffic. (Source: Gabby Sellam, Episode #218)
- Do not use generic section headers like "Key Features," "Why Choose Us," or "User Benefits." Replace them with outcome-driven language. (Source: Scott Cappuzzo, Episode #251)
- Do not list all services or offerings in the hero section. Choose one primary message above the fold. (Source: Gabby Sellam, Episode #218)
Sources
| Episode | Guest | Date |
|---|---|---|
| Episode #251 | Guy Yalif | 2025-06-02 |
| Episode #251 | Scott Cappuzzo | 2025-06-02 |
| Episode #251 | Talia Wolf | 2025-06-02 |
| Episode #231 | Talia Wolf | 2025-03-24 |
| Episode #224 | Ross Simmonds | 2025-03-03 |
| Episode #222 | Robert Kaminski | 2025-02-24 |
| Episode #220 | Diane Wiredu | 2025-02-17 |
| Episode #220 | Lee Reshef | 2025-02-17 |
| Episode #218 | Gabby Sellam | 2025-02-10 |
| Episode #218 | Tas Bober | 2025-02-10 |
| Episode #218 | Will Hoekenga | 2025-02-10 |
| Episode #216 | Bill Wilson | 2025-02-03 |
| Episode #185 | Tas Bober | 2024-10-17 |
| Episode #181 | Will Hoekenga | 2024-10-03 |
| Episode #178 | Dave Gerhardt | 2024-09-23 |
| Episode #154 | Tas Bober | 2024-07-01 |
| Episode #132 | Talia Wolf | 2024-04-15 |
| Episode #119 | Peep Laja | 2024-02-22 |
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.