The Athletic Audit

Observed Behavior: The Athletic’s free article meter (typically 1-2 free articles per month) does not sync across devices. A user can read their free articles on desktop Chrome, then read additional free articles on mobile Safari and in an incognito window. The meter also resets when the user clears cookies.

Technical Root Cause: The meter count is stored client-side in cookies and localStorage rather than being tracked server-side against a fingerprint or anonymous user profile. There is no cross-device sync mechanism for non-authenticated users.

Business Impact: Power users who discover the meter bypass read premium content indefinitely without subscribing, directly undermining the paywall’s revenue function. This is particularly damaging because The Athletic’s most engaged readers — the ones most likely to convert — are also the most likely to discover workarounds.

Remediation Path: Track meter usage server-side using a combination of IP address hashing and browser fingerprinting for anonymous users. For users who sign in to read free articles (a common pattern), sync the meter to their account. Accept that some bypass will always exist, but close the most obvious vectors.

Observed Behavior: When a user starts an embedded podcast episode on an article page and then navigates to a different article, the audio continues playing in the background with no visible player controls on the new page. The user cannot pause, scrub, or control the audio without navigating back.

Technical Root Cause: The audio player is instantiated within the article component and attached to a global <audio> element. When the article component unmounts during route navigation, the React cleanup function does not call audio.pause() or remove the element from the DOM.

Business Impact: Uncontrollable background audio is a jarring user experience that interrupts reading on the new page. Users must either find the original tab/page or mute their entire device, creating a negative association with The Athletic’s podcast content.

Remediation Path: Implement a persistent mini-player that appears in a fixed footer position when the user navigates away from a page with active audio. The mini-player should include play/pause, scrub bar, and a close button. On beforeunload or route change, if no mini-player is present, pause the audio.

Observed Behavior: Clicking the “Subscribe” button on the newsletter signup form rapidly results in multiple confirmation emails being sent for the same email address. Users report receiving 3-5 identical welcome emails.

Technical Root Cause: The form submission handler does not disable the button or implement a debounce/mutex during the async API call. The server-side endpoint also lacks idempotency — it creates a new subscription record for each request rather than deduplicating by email.

Business Impact: Multiple welcome emails signal a lack of polish and can trigger spam filter flags, potentially causing future newsletters to land in spam. For a brand built on premium quality, this undermines first impressions.

Remediation Path: Disable the submit button and show a loading state immediately on click. On the server, enforce email uniqueness constraints and return a 200 (not 201) for duplicate subscriptions. Implement a client-side cooldown of 5 seconds after successful submission.

Observed Behavior: Subscribers who save articles for offline reading in the mobile app and later reconnect to the network occasionally see articles revert to an older version. This is visible when articles have been updated with corrections or score updates.

Technical Root Cause: The offline sync mechanism uses a last-write-wins strategy based on the device’s local timestamp. When the device clock drifts or the sync queue processes out of order, the stale cached version overwrites the server’s updated version in the local database.

Business Impact: Readers see outdated information (wrong scores, pre-correction text) without any indication that the content has been updated. This is particularly problematic for time-sensitive content like trade deadline coverage or game recaps.

Remediation Path: Replace timestamp-based conflict resolution with server-side version numbers. On sync, compare the local version number against the server’s current version and always prefer the higher version. Display a subtle “This article has been updated” notice when the synced version differs from the cached version.

Observed Behavior: Non-subscribers reading a free article hit the paywall mid-paragraph. The content cuts off mid-sentence, the remaining text is blurred, and a subscription overlay covers 60% of the viewport. The transition is abrupt — there is no visual warning that the free content is about to end.

Technical Root Cause: The paywall insertion point is calculated by character count rather than semantic paragraph boundaries. The blur effect is applied to the DOM element immediately following the cutoff point, which can be mid-sentence.

Business Impact: Mid-paragraph interruption feels hostile rather than persuasive. Users who were engaged with the content’s narrative flow are jolted out of their reading state. Research shows that clean break points (between paragraphs, after a compelling insight) convert at higher rates than abrupt cutoffs.

Remediation Path: Calculate the paywall insertion point at the nearest paragraph boundary after the character threshold. End the free content on a cliffhanger paragraph that demonstrates the article’s value. Replace the blur with a clean fade-to-white gradient and a compelling, content-specific CTA: “This story continues with an analysis of [topic]. Subscribe to read the full piece.”

Observed Behavior: After finishing a long-form article, the comment section displays a loading spinner for 2-4 seconds before comments appear. If the user navigates to comments from a push notification link, they see the spinner on an otherwise empty page until the comments and the parent article both load.

Technical Root Cause: The comment system is a separately deployed microservice with its own API. Comments are fetched via a client-side call that fires only after the article component fully renders, creating a sequential loading waterfall.

Business Impact: The Athletic’s comment section is a premium feature and a key subscriber retention tool — subscribers cite the quality of community discussion as a reason they pay. Slow comment loading reduces engagement with this differentiating feature.

Remediation Path: Prefetch the comments API call in parallel with the article content fetch. Render comment count and the top 3 comments in the initial server response so users see an active discussion immediately. Lazy-load the full comment thread as the user scrolls to the bottom.

Observed Behavior: The Athletic’s podcast library pages display episodes in reverse chronological order with no ability to filter by topic, sport, or team. A user looking for a specific episode about the NFL Draft must scroll through months of content to find it.

Technical Root Cause: The podcast page is a simple paginated list rendering episodes from the RSS feed. No taxonomy, tagging, or search functionality was built for the podcast content type.

Business Impact: Podcast content represents significant production investment but is functionally undiscoverable on the website. Users who want to explore the podcast library default to Apple Podcasts or Spotify, where they are outside The Athletic’s ecosystem and cannot be converted or retained.

Remediation Path: Add sport/team filters and a text search to the podcast page. Tag episodes with relevant teams and topics at publish time. Surface “Related episodes” on article pages where a relevant podcast discusses the same topic, creating cross-format engagement.

Observed Behavior: The newsletter preferences page lists 40+ individual newsletter options in a single scrollable list with no categorization. Each newsletter shows its name and a one-line description, but there is no indication of frequency (daily, weekly, event-triggered) or content type (analysis, news, podcast recap).

Technical Root Cause: The preference page was built when The Athletic had 8 newsletters and has not been redesigned as the newsletter portfolio expanded. New newsletters are appended to the bottom of the list.

Business Impact: Users overwhelmed by the number of options either subscribe to nothing (missing retention-critical touchpoints) or subscribe to everything and quickly experience email fatigue, leading to a bulk unsubscribe that removes them from all newsletters.

Remediation Path: Group newsletters by sport and content type. Show frequency badges (Daily, Weekly, Game Days). Default new subscribers to a curated “Starter Pack” of 3-4 newsletters based on their team preferences, with a “Discover more” section for the full catalog.

Observed Behavior: New visitors from Google search are allowed 1 free article before hitting the hard paywall. First-time visitors who arrive on a single article and are immediately blocked have no opportunity to experience The Athletic’s quality across multiple pieces or writers.

Technical Root Cause: The paywall meter is set to a uniform limit regardless of the user’s acquisition channel. A user arriving from a paid social ad receives the same 1-article allowance as a user arriving from organic search.

Business Impact: A 1-article limit converts at roughly 0.3% for cold traffic from search. Increasing the limit to 3 articles for first-time visitors from non-branded search queries has been shown to increase trial starts by 40%+ across comparable subscription publishers, as users need multiple exposures to assess content quality.

Remediation Path: Implement channel-aware metering: allow 3 free articles in the first 7 days for users arriving from organic search or social referrals, 1 article for direct/returning visitors. Track conversion rates by meter limit cohort to find the optimal balance between free sampling and conversion urgency.

Observed Behavior: When purchasing a gift subscription, the buyer is asked to enter the recipient’s email. However, the gift cannot be activated unless the recipient creates a full account (name, password, newsletter preferences) before accessing any content. The activation email does not clearly explain this requirement.

Technical Root Cause: The gift redemption flow uses the same account creation form as the standard subscription flow. There is no streamlined “magic link” activation path for gift recipients.

Business Impact: Gift subscriptions are a key acquisition channel for reaching users who would never self-select into a paid sports journalism product. Every friction point in the activation flow wastes the acquisition cost that the gifter already paid.

Remediation Path: Allow gift recipients to start reading immediately via a magic link. Defer account creation (password, preferences) until after the user has read 2-3 articles and experienced the product’s value. Pre-fill the account with the recipient’s email from the gift purchase.

Observed Behavior: The pricing page shows the monthly price ($9.99/month) and annual price ($71.99/year) side by side, but the annual savings are not explicitly calculated. Users must do mental math to realize the annual plan saves ~40%. The monthly plan is visually highlighted as the default.

Technical Root Cause: The pricing component renders both plans with equal visual weight. The monthly plan appears first (left position on desktop, top position on mobile) and has the primary-colored “Subscribe” button.

Business Impact: Annual subscribers have dramatically lower churn rates than monthly subscribers. By not clearly communicating the annual savings and defaulting to monthly, The Athletic is optimizing for initial conversion at the expense of subscriber lifetime value.

Remediation Path: Default to the annual plan with the monthly plan as the secondary option. Show explicit savings: “Save 40% — just $5.99/month billed annually.” Use an annual/monthly toggle with the savings callout animating when the user switches, making the value differential visceral.

Observed Behavior: Below paywalled articles, The Athletic displays a generic “Subscribe for unlimited access” message with no preview of what else the subscriber would unlock. There is no sampling of other premium content, trending stories, or author highlights.

Technical Root Cause: The below-paywall area uses a static subscription prompt component with no dynamic content injection. The component was designed once and has not been iterated.

Business Impact: Users who hit the paywall and scroll past it are demonstrating intent — they want to see if there is enough value to justify subscribing. A static prompt fails to answer their implicit question: “Is there more content worth paying for?”

Remediation Path: Below the paywall, dynamically surface 3-5 headline previews of trending subscriber-only articles, the most popular articles from the user’s detected sport interest, and a rotating author spotlight. This transforms the paywall dead-end into a content discovery surface that reinforces the value proposition.

Observed Behavior: The Athletic’s paywalled articles do not include the isAccessibleForFree property in their structured data. Google’s guidelines require publishers using “flexible sampling” (metered paywall) to mark paywalled content with isAccessibleForFree: false and wrap the paid content in a cssSelector within hasPart. Without this, Google may stop indexing paywalled content.

Technical Root Cause: The article JSON-LD template was implemented before Google’s paywall structured data requirements were published and was never updated.

Business Impact: Non-compliance with Google’s paywall guidelines risks removal of paywalled articles from the index entirely. Given that organic search drives the top of The Athletic’s subscription funnel, this is an existential SEO risk.

Remediation Path: Add isAccessibleForFree: false to the NewsArticle JSON-LD schema. Include a hasPart property with isAccessibleForFree: false and a cssSelector pointing to the paywalled content container. Follow Google’s structured data documentation for subscription and paywalled content exactly.

Observed Behavior: Article bylines display the author’s name and link to their author page, but the JSON-LD schema uses a plain text string for the author field rather than a Person entity with url, name, and sameAs properties.

Technical Root Cause: The schema template was built with a simplified author: "Name" pattern rather than the expanded author: { "@type": "Person", "name": "...", "url": "..." } format.

Business Impact: The Athletic’s writers are its primary competitive advantage — subscribers cite specific journalists as their reason for paying. Without proper Person entity markup, Google cannot build Knowledge Graph associations between The Athletic’s star writers and their content, reducing the visibility of author-specific search queries.

Remediation Path: Expand the author field to a full Person entity including name, url (to the author’s page on The Athletic), and sameAs (linking to their Twitter/X profile). This helps Google associate content with specific journalist entities and can surface author carousels in search results.

Observed Behavior: Some articles published on The Athletic are also syndicated to NYTimes.com. Both versions carry rel="canonical" tags pointing to their own URLs, creating competing canonical signals. Google is inconsistently choosing the NYT version for some articles, even when The Athletic’s version was published first.

Technical Root Cause: The syndication pipeline copies articles to the NYT CMS without updating the canonical tag to point back to the original Athletic URL. Each CMS independently generates self-referencing canonical tags.

Business Impact: When Google indexes the NYT version instead of The Athletic’s, the organic traffic and link equity flow to NYTimes.com rather than theathletic.com. This undermines The Athletic’s domain authority on sports topics and the effectiveness of its SEO investment.

Remediation Path: Syndicated content on NYTimes.com must carry a rel="canonical" tag pointing to the original Athletic URL. Implement a cross-domain canonical tag injection in the syndication pipeline. For articles that should live on NYT (editorial decision), add a rel="canonical" on The Athletic’s version pointing to NYT. Never have both versions self-canonicalize.

Observed Behavior: The Athletic’s explainer articles (“What you need to know about the NBA trade deadline,” “How does the NFL draft order work?”) are structured as long-form narratives without semantic question-and-answer markup. These high-search-volume informational queries are dominated by competitors using FAQ schema to win featured snippets.

Technical Root Cause: The CMS does not support FAQ-type content blocks, and articles are authored as continuous prose without structured Q&A sections.

Business Impact: Featured snippets for sports informational queries drive significant top-of-funnel traffic. The Athletic’s well-researched explainer content is more authoritative than competing listicles but loses the SERP feature because it lacks the structured data that Google needs.

Remediation Path: For explainer and FAQ-style articles, add FAQPage JSON-LD schema with the key questions and concise answers extracted from the article body. Add a CMS content block type for Q&A pairs that automatically generates FAQ schema on publish.