Attention Arc is hiring for a Discovery team that checks how brands show up in Google, ChatGPT, Gemini and Perplexity and audits "website content, metadata". Its own homepage ships an empty meta description, no headings and no structured data; the only words in the HTML are the cookie banner. The services, the $500MM+ billings and the client list live in a JavaScript object, so any reader that does not run scripts, including many AI crawlers and link previews, sees a consent notice instead of an agency.
First action
Ask ChatGPT, Perplexity and Gemini "What does Attention Arc do?" and save the answers as a baseline.
How to measure it
Correct answers in tracked prompts
- Now
- –
- Target
- 8 of 10
- By
- 60 days
Steps
Baseline
Ten prompts across Google and three assistants.
Paid Social & Discoverability Co-op 1 day
Server-render
Output the homepage copy as HTML; keep the app for animation.
Web Developer 1 week
Add headings and meta
One H1, section H2s, a meta description per page.
Discovery Lead (The Intent Capturers) 1 day
Add schema
Organization with parent company, offices and leaders.
Discovery Lead (The Intent Capturers) 1 day
Repeat
Leadership and careers pages.
Web Developer 3 days
Re-test
Same ten prompts monthly.
Paid Social & Discoverability Co-op monthly
Why it works
Render the page copy into the HTML on the server (or pre-render the Vue app), with one H1 ("Restoring Intention to Media"), real H2s for Strategy, Activation and Measurement, a meta description, and Organization schema naming the agency, Cheil, the offices and the leaders. Then run the co-op's visibility research on Attention Arc itself before and after.
Search and AI answers can only describe what they can read. Fixing the agency's own site is also the best proof of the Discovery service it is building.
Ready to use
ChecklistReadable-site checklist
[ ] Homepage copy in the HTML response [ ] One H1 and section H2s [ ] Meta description on every page [ ] Organization schema (parent, offices, leaders) [ ] Leadership and careers pages rendered too [ ] Text-only fetch shows services and stats [ ] Baseline and monthly AI prompt checks
Risks and how to handle them
Breaking the animated design
Render the HTML first and let the app enhance it.
Duplicate text for users
Hide nothing; render once.
Evidence
- Your websiteHomepage HTML (fetched twice on October 23, 2026): title "Modern Media Strategy & Performance Marketing | Attention Arc", an empty meta description, no headings and no structured data. The only readable text in the page body is the cookie banner (about 240 words); all the agency's copy sits inside a JavaScript data object that the app renders in the browser. An og:description is set for social previews.Source
- HiringPaid Social & Discoverability Co-op (Phoenix, posted October 8, 2026), working with the Activation team and the "Discovery team, The Intent Capturers", which "helps brands show up where people search, explore, and make decisions": paid social on "Meta, TikTok, LinkedIn, Pinterest, Reddit"; SEO, "Generative Engine Optimization (GEO), and Answer Engine Optimization (AEO)"; "Research brand visibility across Google, ChatGPT, Gemini, Perplexity"; "evaluating website content, metadata, internal linking"; Google Search Console, GA4 and Semrush.Source
- Your websiteHomepage copy (as rendered): "Restoring Intention to Media."; "brings together the strengths of McKinney Media and LWD"; services Strategy, Activation and Measurement, with planning across "linear TV, CTV, OTT, OLV, audio, programmatic, paid social, SEO, paid search, OOH, and print"; "$500MM+ Annual Media Billings", "150+ Media Experts"; tools "ClientIQ, AudiencePro, and SmartMatch360"; client logos including Sherwin Williams, Nikon, HomeServe, Pulte Group, Tommy John, National Debt Relief, Burlington, Tranzact, First Citizens Bank and Plymouth Rock Assurance; one contact form ("Let's Talk").Source
- Google PageSpeedMobile lab test: performance score 39, Largest Contentful Paint 28.9 s, and the LCP element is the intro paragraph, which appears only after the app loads. Real visitors (Chrome UX Report) see LCP of 0.95 s, INP of 72 ms and no layout shift, so humans on fast connections are fine; the issue is what non-rendering readers see.Source