Before we run the audit, we need to make sure we're asking the right questions about the right competitors to the right buyers. This document presents what we've learned about Pursue ATL's market — your job is to tell us what we got right, what we got wrong, and what we missed.
Pursue ATL's entire pitch is being the one discoverable "room" for Atlanta builders — so before the audit measures citation visibility, these three signals tell us whether AI engines can even reach and trust the site.
Disallow: / to GPTBot, ClaudeBot, Google-Extended, and Bytespider, hard-blocking the entire site from the crawlers that feed ChatGPT, Claude, and Google's AI. This caps the ceiling on every other optimization.lastmod entirely, so the weekly Monday-4am refresh is invisible to crawlers (see Site Findings). Verify dates manually.lastmod timestamp. ChatGPT-User and PerplexityBot remain allowed under the wildcard rule, so a thin slice of real-time fetch traffic still reaches the site.AI assistants are quickly becoming how founders, operators, students, and builders decide where to plug into a local tech scene — when someone asks ChatGPT or Claude "where do Atlanta builders actually hang out," the answer they get shapes who shows up. For a free, application-only community whose whole reason to exist is being the connective layer over a fragmented ecosystem, being the cited answer to those questions is the growth engine. Establishing that visibility early compounds: the communities AI engines learn to trust now become the default recommendation as the behavior goes mainstream.
This Foundation Review presents three things for you to validate before the audit runs: the competitive landscape that competes for builders' attention and shapes how we construct head-to-head queries, the buyer personas — here, the people deciding whether to apply and invest their time — that determine what gets searched, and the Layer 1 technical baseline that determines whether AI engines can access your content at all. Think of it as confirming together that we're pointing the audit at the right market before a single query runs.
The validation call is a working session with real stakes. It produces two kinds of decisions: input validation (are the right competitors in the right tiers, are the right people in the persona set, do the strength ratings hold up?) and engineering triage (which technical fixes can your team start on immediately, without waiting for results?). The TL;DR below names the specific items on both tracks.
lastmod from the Monday 4am sync — advertises the calendar's weekly refresh to crawlers and doesn't depend on anything decided at the call.Purpose This is the foundation for a GEO (Generative Engine Optimization) visibility audit of Pursue ATL in the Atlanta builder-community and events-discovery space. It captures the competitors, buyer personas, capabilities, and buyer pain points that will drive the buyer query set, plus the Layer 1 technical findings from your site. Get these inputs right and the audit measures the right things.
Your Job Confirm what's accurate, correct what's wrong, and flag what's missing. Pay special attention to anything marked Medium or Low confidence and to the purple questions throughout — those are the places where your answer changes how the audit is built.
Confidence Badges Every entity carries a confidence badge. High = sourced directly from your site or strong category signals. Medium = reasonable inference that needs your confirmation. Low = a hypothesis we're least sure of. Higher-confidence items still deserve a sanity check, but the lower ones are where your input matters most.
→ Pursue ATL reads as two things at once — an events-aggregation layer that pulls Atlanta Tech Village, ATDC, and Eventbrite listings into one calendar, and a destination community people join. Do builders search for it as "the Atlanta builder community" or as "the Atlanta tech events calendar"? If both, we split into two query clusters; if one dominates, we concentrate there — and we need to know whether to treat "Pursue Networking" (the parent brand) as the same entity in brand queries.
6 personas: 4 decision-makers, 1 evaluator, 1 influencer. These are the people who decide whether to apply and invest their time — and each one searches for a builder community differently, which is exactly what drives the query set.
Critical Review Area Personas are the single biggest lever on the audit. If we have the wrong people — or miss someone who shows up in your community — we ask the wrong questions and measure visibility against the wrong intent. Scrutinize the role definitions and the influence labels closely.
Data Sourcing Note Names, roles, seniority, technical level, and veto power come straight from the knowledge graph. Because Pursue ATL is a free community rather than a B2B purchase, "veto power" reflects that the join decision is the individual's alone — which is why most personas read as decision-makers. The buying jobs and query focus areas are synthesized from each persona's role to show how they'd search; confirm or redirect them.
→ Is the core member a pre-seed solo founder, or are funded founders the heavier share of your community? If funded, capital and investor-intro queries gain weight; if pre-seed-solo, peer-support and co-founder queries dominate.
→ Do technical AI builders search differently enough from generalist founders (Marcus) to warrant their own AI-builder query cluster, or do they overlap so much we'd be testing the same queries twice?
→ Do students self-select into Pursue ATL the way founders do, or do they arrive through campus orgs like GT Startup Exchange? If the latter, student queries belong in a campus-adjacent cluster and that competitor's tier firms up as primary.
→ Do operators decide to join on their own, or arrive because their founder is already in? If they don't self-select, we drop the dedicated operator query cluster and fold their intent under the founder personas.
→ Is Jordan a member or a partner? If ecosystem builders engage to source deals and promote events rather than to "join," their queries belong in a partner/organizer cluster — distinct from the member-acquisition queries that are the audit's center of gravity.
→ This persona is inferred, not observed — do relocated/newcomer founders actually show up as a distinct group in your community? If they overlap entirely with Marcus or Devon, we merge and drop the "how to break in" newcomer queries; if real, they justify their own discovery cluster.
Missing Personas? These roles sometimes appear in builder-community deal flow — do they show up in yours? (1) Corporate innovation / accelerator program scout (if companies use the community to find startups to partner with). (2) Angel / micro-VC sourcing locally (if investors lurk for deal flow as a distinct motion from Jordan's organizer role). (3) Career-switcher / aspiring builder not yet founding (if "I want to get into tech" people join to learn before building). Each would warrant its own query cluster. Who else shows up in your community?
6 primary + 4 secondary competitors. Tier assignments here decide which head-to-head matchups the audit tests — and for Pursue ATL, "competition" means rival claims on a builder's time and attention, not feature-for-feature product comparison.
Why Tiers Matter Tier drives which competitors get direct head-to-head queries — things like "best free community for Atlanta startup founders," "Atlanta Tech Village alternatives," or "Pursue ATL vs TECH404." With 6 primary competitors that's roughly 36–48 differentiation queries. We're least certain on three primary tiers — Georgia Tech Startup Exchange, Mond(AI)y Coffee, and Atlanta Startup Village (all Medium). Note too that several "competitors" — Atlanta Tech Village, ATDC — are also event sources Pursue ATL aggregates, so they're partners and rivals at once. If any of the three uncertain names rarely come up when a builder is choosing where to plug in, moving them to secondary shifts ~6–8 queries each out of the head-to-head set.
→ Three questions before we lock tiers: (1) Missing rivals — does anyone else compete for the same builders (Founder Institute Atlanta, Endeavor Atlanta, specific Discord servers)? (2) Tier accuracy — should Mond(AI)y Coffee (a single recurring event) and Georgia Tech Startup Exchange (student-only) really sit at primary, or are they secondary attention-rivals? (3) Partners vs. competitors — Atlanta Tech Village and ATDC are also event sources you aggregate; do you want the audit to frame them as head-to-head rivals at all, or strictly as the ecosystem you sit on top of?
11 buyer-level capabilities mapped, rated outside-in. These determine which capability queries the audit tests — and the strength ratings tell us where to play offense versus defense.
A community where everyone is actually a builder, not recruiters or spam — application-only with real vetting.
A live, active place to ask questions, share wins, and get answers from other founders any time — not a dead Slack.
One place to see every Atlanta tech event worth attending instead of hunting across Eventbrite, Luma, and Meetup.
A weekly digest that keeps me on top of AI news and local Atlanta opportunities without doomscrolling.
Plug into a serious founder community without paying for coworking, membership dues, or a program.
Get pointed to the right people, channels, and events for what I'm building instead of figuring it out alone.
Recurring live face time to get real feedback and talk through problems with other builders.
Find and reach the right co-founder, collaborator, or first hire inside the community.
A coworking space and regular in-person events where I can show up in real life and build relationships.
A real accelerator, curriculum, or assigned mentors that move my company forward, not just networking.
Warm intros to investors, grants, or demo days that actually help me raise money.
Strong Across Five Capabilities Pursue ATL rates Strong on five capabilities — the audit tests all 11, but differentiation queries will emphasize three. Which of these five best represents where Pursue ATL actually wins builders away from the alternatives?
Worth noting: three of the four lowest ratings — in-person space, structured programming, capital access — are exactly where Atlanta Tech Village and ATDC are strongest, so those become defensive ground.
→ Three checks on the ratings: (1) Accuracy vs. named rivals — is "Always-On Builder Chat" genuinely stronger than TECH404's 3,000-member Slack, and is "Curated Membership" a real edge buyers feel? (2) The inferred weak/absent trio — in-person space (weak), structured programming (weak), and capital access (absent) are llm-inferred; if Pursue ATL plans to add IRL events, programming, or investor intros, those ratings change and we test those queries. (3) Merge candidates — do "AI-Powered Onboarding" and "Member Directory" describe one capability (getting matched to the right people) or two distinct ones?
10 pain points: 5 high, 5 medium severity. The buyer language here is how queries get phrased — these are the frustrations that send a builder to an AI assistant in the first place.
→ Three things to pressure-test: (1) Severity — is "founders can't find collaborators" really High and "communities don't open investor doors" only Medium (and that last one is our Low-confidence call), or does your community feel them in a different order? (2) Buyer language — does "every founder Slack turns into a ghost town" match how your members actually describe the problem, since several of these are inferred rather than pulled from member reviews? (3) Missing pains — do builders also come to you frustrated about finding their first local customers/beta users, FOMO on who's raising, or imposter syndrome among non-technical founders? Any of those would seed its own query set.
These are the technical signals that determine whether AI engines can access and parse pursueatl.com. They're handed off to engineering now — they don't wait for the validation call.
Engineering — Start Immediately One critical blocker dominates everything else: major AI crawlers are blocked at the root. The robots.txt issues a Cloudflare-managed Disallow: / to GPTBot, ClaudeBot, Google-Extended, and Bytespider, so the crawlers that feed ChatGPT, Claude, and Google's AI cannot ingest a single page. No other optimization matters until this is fixed. Two further diagnostic items — the sitemap missing every lastmod timestamp and three near-empty partner-org pages — are medium-severity and worth fixing in the same pass. Engineering should treat unblocking the crawlers as the priority-zero task.
What we found: The robots.txt at pursueatl.com is a Cloudflare Managed Robots block that issues Disallow: / to a list of AI crawlers, hard-blocking the entire site from them: GPTBot (OpenAI), ClaudeBot (Anthropic), Google-Extended (Google's AI/Gemini crawler), Bytespider (ByteDance/TikTok), plus Amazonbot, Applebot-Extended, CCBot, and others. The wildcard group also carries Content-Signal: search=yes, ai-train=no, expressly reserving rights against AI training. Notably, ChatGPT-User (browse mode) and PerplexityBot are NOT named and remain allowed under the permissive wildcard, so a narrow slice of real-time fetch traffic still reaches the site.
Why it matters: These blocked agents populate the indexes and grounding corpora behind ChatGPT, Claude, Google AI Overviews/Gemini, and TikTok's AI. With them disallowed at the root, none of Pursue ATL's pages — the join flow, the events calendar, the Concierge offer, the partner-org pages — can be ingested by those engines. For a community whose entire value proposition is being the discoverable "one room" for Atlanta builders, being invisible to the dominant answer engines directly undercuts the goal of this audit, and caps the ceiling on every other optimization. This isn't an exotic misconfiguration — Cloudflare changed its default to block AI crawlers in July 2025, and Cloudflare handles roughly 24% of all web traffic (Cloudflare, July 2025), so the default catches many sites unintentionally.
Recommended fix: Disable or override the Cloudflare "Block AI bots / Managed Robots" setting for the crawlers the client wants visibility in (at minimum GPTBot, ClaudeBot, Google-Extended) — in the dashboard this is under AI Crawl Control / robots.txt management — or publish a custom robots.txt allowing those user-agents. Decide deliberately per crawler (allowing real-time grounding while restricting training is a legitimate stance), then re-test with each user-agent after the change.
What we found: sitemap.xml exists and is well-formed, listing all 14 URLs, but not a single <url> entry carries a <lastmod> value. The partner-org event pages aggregate time-sensitive data re-synced weekly (the /events page reports "data pulled every Monday at 4am"), yet none of that recency is exposed to crawlers.
Why it matters: AI and search crawlers use <lastmod> as a primary signal for what to re-crawl and how fresh a page is. Event-aggregation pages are inherently freshness-sensitive; without lastmod, crawlers can't tell these pages update weekly and may treat them as stale. Freshness is a heavily weighted citation factor — AI-cited content runs about 25.7% fresher on average than content in traditional Google results (Ahrefs, August 2025) — so advertising the weekly refresh is low-cost leverage.
Recommended fix: Populate <lastmod> for every URL, driven by the actual last content/sync date (the Monday 4am refresh is a natural source for the event pages). Regenerate the sitemap as part of the weekly sync job so timestamps stay current automatically.
What we found: Three of the ten partner-org pages in the sitemap — /events/organizations/russell-center, /ama-atlanta, and /connect-georgia — currently display a one-line org description and an "Upcoming events" heading with no events beneath it. They're publicly indexed but contain almost no substantive, extractable content (content_depth scored 0.30).
Why it matters: Indexed pages that resolve to a heading and one sentence read as low-value or soft-404-like to crawlers and offer nothing for an AI engine to cite. They can dilute the perceived quality of the /events/organizations/ section as a whole, and the point of these pages — surfacing what's happening at each org — isn't being delivered when the list is empty.
Recommended fix: For orgs with no current events, either (a) suppress the page from the sitemap and add noindex until events exist, or (b) enrich it with persistent, evergreen content (what the org does, recurring program names, how to get involved, a link to their calendar) so it carries value between events. Reserve indexing for pages that deliver real content.
What we found: On the homepage, the rendered output surfaced two top-level (H1-level) headings — "Atlanta's Discord for builders · open now" and "Atlanta has a thousand rooms. This is the one you need." Multiple H1s flatten the document outline so crawlers can't tell which heading is the page's primary subject. (Heading-level inference from rendered markdown is approximate — confirm against raw HTML.)
Why it matters: A clean single-H1, properly nested outline lets AI engines map a page's structure and treat headings as passage labels for citation. Competing H1s weaken that signal on the site's most important page. The inner pages (/apply, /concierge) already use a clean single-H1 hierarchy, so this is an isolated, easy correction.
Recommended fix: Demote one of the two homepage H1s so a single H1 names the page's primary subject, with the secondary line as an H2 or styled subhead. Verify the final heading outline in view-source or an SEO crawler.
The following items could not be assessed through our analysis method (rendered markdown). We recommend your engineering team verify these manually before the validation call.
What to check: Our analysis reads rendered page text, not raw HTML, so JSON-LD blocks aren't visible to it. Several pages have obvious schema opportunities: Event/ItemList schema on /events and the 10 partner-org pages, FAQPage schema on /concierge (it has a six-question FAQ), Organization schema site-wide, and Offer/Product schema for Concierge pricing.
Recommended action: Verify current JSON-LD with Google's Rich Results Test on /events, a representative org page, /concierge, and the homepage. Where absent, add Event/ItemList to the calendar and org pages, FAQPage to /concierge, and Organization schema sitewide.
What to check: Because our method reads rendered text rather than the HTML <head>, we couldn't inspect meta description or OG/Twitter Card tags on any page, or confirm whether they're present, unique, and accurate.
Recommended action: Spot-check the <head> (view-source or a social-preview tool) on the homepage, /events, /concierge, /apply, and a representative org page. Ensure each page has a unique, descriptive meta description and complete OG tags (title, description, image, url).
What to check: The site appears built on a JavaScript framework and the /events calendar is dynamically populated. In our fetches every page — including the calendar with ~148 events — returned full rendered text, a positive sign of server/pre-rendering, but our tooling can't definitively confirm what a crawler sees with JS disabled.
Recommended action: Verify with JavaScript disabled (or "view rendered source" vs. raw fetch, or Search Console's URL Inspection) that /events and the org pages serve event content in the initial HTML. If any content is client-only, add server-side rendering or pre-rendering for crawler requests — this matters most once robots.txt is opened up.
Read These Numbers Carefully Coverage is complete (all 14 sitemap URLs analyzed), but two metrics rest on thin data: freshness shows 1.0 only because a single page carried a detectable date — 13 of 14 have no date signal at all, which is the same gap the missing-lastmod finding describes — and schema coverage couldn't be scored on any page because our method reads rendered text, not raw HTML. Both belong on the manual verification list above before we treat them as settled.
Why Now GEO is a time-sensitive opportunity for Pursue ATL:
Once the crawler block is lifted, the full audit will measure how Pursue ATL shows up across the queries builders actually ask — "best free community for Atlanta startup founders," "where do Atlanta builders hang out," "Atlanta Tech Village alternatives," "Atlanta tech events this week." You'll see exactly which of those return answers naming TECH404, Atlanta Tech Village, or ATDC but not Pursue ATL — and what it would take to appear in them. Fixing the Layer 1 issues now means the audit measures a site AI engines can finally read, so the baseline reflects your real content, not a blocked door.
A 45–60 minute working session to walk through this document — confirm the personas, competitors, features, and pain points, and answer the open questions that shape the query set.
We build the buyer query set from the validated inputs and run it across the selected AI platforms to measure where Pursue ATL is and isn't cited.
Visibility analysis, competitive positioning, and a prioritized three-layer action plan — including the content recommendations this Foundation Review deliberately holds until we have query data to rank them.
Start Now — Engineering Three Layer 1 fixes don't depend on the rest of the audit and will improve your baseline visibility before we even measure it: (1) Override the Cloudflare Managed Robots AI-bot block so GPTBot, ClaudeBot, and Google-Extended can reach the site — this is priority zero, because everything else is capped while it's in place. (2) Populate sitemap lastmod timestamps from the Monday 4am sync job so crawlers see the weekly refresh. (3) Fix the homepage dual-H1 so the site's most important page has a single clear subject. After unblocking, re-test each AI user-agent to confirm access.
Two jobs before we meet. The questions on the left require your judgment — no one knows your community better than you. The engineering tasks on the right don't require the call at all.