Wiza Organic Growth Opportunities

This play creates a massive library of pages detailing the most common email patterns and deliverability insights for millions of corporate domains. It captures high-intent users who are manually trying to guess or verify contact information before they turn to a paid tool.

Example Keywords

• "{company} email format"
• "{domain} email pattern"
• "how to find email addresses for employees at {company}"
• "verify {domain} email addresses"
• "common email patterns at {company}"

Rationale

Users searching for specific company email formats are actively prospecting and represent a high-conversion audience. By providing these patterns for free, Wiza can position its live verification tool as the automated solution to this manual problem.

Topical Authority

Wiza's current organic footprint is already built on a directory of person-level pages, signaling to Google that the domain is a trusted source for identity and contact data. Expanding into domain-level patterns is a natural topical extension of this existing authority.

Internal Data Sources

Use Wiza's internal database of observed email pattern distributions (e.g., % first.last vs. firstinitiallast) and aggregate verification outcomes to provide unique, data-backed deliverability insights.

Estimated Number of Pages

50,000 - 250,000+ (Covering top global domains and long-tail corporate entities)

This strategy generates landing pages for specific job functions within various industries, offering curated "pre-built" list views. It targets users looking for bulk lead data rather than individual contact lookups, significantly increasing the commercial value of the traffic.

Example Keywords

• "{job title} email list"
• "{industry} {job title} contact list"
• "buy {job title} leads"
• "{job title} leads database"
• "verified {job title} emails in {industry}"

Rationale

These pages align perfectly with Wiza's core product offering—a B2B lead database. By capturing users searching for "lists," Wiza can bridge the gap where competitors like Apollo currently yield higher traffic from similar keyword footprints.

Topical Authority

Wiza's existing ranking for "B2B prospecting tool" and "lead database" provides the necessary topical foundation to rank for these more specific, segmented list queries.

Internal Data Sources

Leverage Wiza's lead database to provide aggregate availability counts (e.g., "10k+ verified VP Sales emails available") and field coverage statistics to differentiate the content from generic competitors.

Estimated Number of Pages

10,000 - 80,000+ (Based on combinations of 200+ roles and 400+ industries)

This play builds a comprehensive library of pre-configured Sales Navigator search strings and filter combinations for specific personas. It captures users at the very beginning of their prospecting workflow on LinkedIn, where Wiza's extension is most valuable.

Example Keywords

• "sales navigator search for {persona}"
• "boolean string for {persona}"
• "sales navigator filters for {industry}"
• "how to find {persona} on sales navigator"
• "best sales navigator filters for {use case}"

Rationale

Wiza's primary user base lives in LinkedIn Sales Navigator. By providing the "recipes" for successful searches, Wiza becomes an indispensable part of the user's workflow before they even need to export data.

Topical Authority

Wiza already has high-performing help articles regarding Sales Navigator exports; expanding this into a library of search strategies leverages that existing technical authority.

Internal Data Sources

Use anonymized title synonym data and common filter combinations from Wiza's most successful user exports to provide "proven" search templates.

Estimated Number of Pages

100,000 - 500,000+ (Covering thousands of persona, industry, and location combinations)

This strategy creates "Companies Like [Company]" pages that help sales teams expand their target account lists based on existing customers. It leverages a lookalike model to provide value to account-based marketing (ABM) practitioners.

Example Keywords

• "companies like {company}"
• "{company} competitors list"
• "similar companies to {company}"
• "companies in the same industry as {company}"
• "find companies similar to {company}"

Rationale

Sellers often prospect by finding peers of their best customers. These pages capture that "expansion" intent and provide a direct path to Wiza's contact enrichment for those newly discovered accounts.

Topical Authority

Wiza's current directory structure already contains company metadata; this play simply re-organizes that data into a high-intent comparison format that Google already associates with the domain.

Internal Data Sources

Utilize Wiza's internal company graph, including industry classifications, employee headcount, and geographic data, to calculate and display similarity scores.

Estimated Number of Pages

300,000 - 1,000,000+ (One page for every major company in the Wiza directory)

This play focuses on the technical integration of Wiza data into the user's existing tech stack, such as Salesforce, HubSpot, or Outreach. It targets bottom-funnel users who are looking for specific automation and enrichment workflows.

Example Keywords

• "{crm} lead enrichment"
• "enrich leads in {platform}"
• "{platform} email verification"
• "how to automate {crm} data enrichment"
• "Wiza integration for {platform}"

Rationale

Integration-related queries have extremely high commercial intent. By providing detailed "playbooks" for each platform, Wiza can attract enterprise-level buyers who prioritize seamless data flow into their CRM.

Topical Authority

Wiza's existing API documentation and integration pages provide a strong technical foundation for Google to rank these more detailed, use-case-specific playbooks.

Internal Data Sources

Incorporate Wiza's API documentation, SDK examples, and real-world customer implementation stories to provide authoritative, technical content.

Estimated Number of Pages

600 - 3,000+ (Covering hundreds of platforms and multiple use cases per platform)

Improvements Summary

Upgrade /d/ person-profile templates to target full name + company + contact-intent modifiers (email, phone, LinkedIn) with stronger on-page relevance. Add hub pages and tighter internal linking so high-volume profiles move from positions ~11–20 into the top 10 while improving CTR and conversions.

Improvements Details

Apply a consistent title/H1/meta formula (e.g., "[Name] at [Company] — Email, Phone & Contact Info | Wiza Directory"), add an 80–120 word above-the-fold summary, "Last updated" + verification module, and 3–5 structured sections (role snapshot, company context, email format, related contacts, FAQ). Add JSON-LD (Person, Organization, BreadcrumbList), build company and role hub pages that link into profiles, add breadcrumbs + related-profile links, and remove indexing noise like "mailto:" strings and raw phone-number blocks while limiting sitemaps to index-worthy profiles.

Improvements Rationale

These pages have low-competition, long-tail demand (e.g., "Matthew Massaro Northwestern Medicine", "Vanessa Otagba") but tend to sit on page 2 due to thin/duplicate templates and weak internal PageRank flow. Cleaner keyword targeting, unique on-page sections, and schema improve entity matching, while hubs and internal links improve crawl paths and rankings; removing "mailto:"/phone-number artifacts prevents Google from misclassifying page topics and reduces index bloat.