Strategic Flow — Ahrefs Changelog Teardown

Source: ahrefs.com/blog/new-features/

Type: Product Changelog

Date: Updated May 1, 2026

Ahrefs Changelog: Running List of New Features

Ahrefs

Product Blog

Product Blog · Updated May 1, 2026

Ahrefs Changelog: Running List of New Features

This is the Ahrefs changelog, a simple list of all our newest features for you to browse.

April 2026

30 Apr

There's a new metric for the Keywords report in GSC Insights: The average position of the highest-ranking URL. This can be useful to monitor when you have multiple URLs ranking for the same term, such as a branded query.

28 Apr

We've massively increased API limits for Lite, Standard and Advanced plans. In this AI era, we're opening up more data to power your marketing. Changes depend on your account level, but as an example, Standard plans now get 2.67x more credits and up to 10x more rows per request.

24 Apr

Grok responses are now available to monitor in Brand Radar for both Ahrefs prompts and custom prompts. It's available in the All indexes add-on or available as a separate subscription.

March 2026

5 Mar

We've launched our new tool: Brand Radar, which lets you track and analyze your brand's presence in AI search.

21 Mar

In Site Explorer's Organic keywords report, see all your keywords across all locations in one place. Traffic dropped? Instantly pinpoint the keywords — and locations — behind it.

February 2026

20 Feb

Group traffic sources by acquisition channel in Web Analytics. See Search, Direct, LLM, Email, Newsletter, and more — all in one view.

6 Feb

We've added a Chat function in AI Content Helper that helps you improve your content for both humans and search engines.

View all plans

⚠ Title announces a filing system, not a value — "Running List of New Features" signals a database entry, not a communication. An SEO who scans this has no reason to slow down or feel the update matters to them.

⚠ The 28 Apr API update is buried in a flat list — 2.67x more credits and 10x more rows per request on Standard plans is a structural change to how every user can work with Ahrefs data. It appears at the same visual weight as "there's a new metric for the Keywords report."

⚠ No hierarchy between major and minor updates — every entry uses identical formatting. The reader cannot scan and identify what requires their attention versus what is background noise.

⚠ "In this AI era, we're opening up more data to power your marketing" is the only hook in the API update — and it arrives mid-paragraph after the feature is already announced. The consequence leads nothing.

⚠ No stat cards — 2.67x, 10x, and 284K newsletter subscribers are buried in prose. The numbers that justify upgrading or changing workflows never get visual treatment.

⚠ CTA "View all plans" is disconnected from every update listed — there is no bridge between what just changed and why right now is the moment to review your plan.

Source: ahrefs.com/blog/new-features/ — Rebuilt

Type: Product Changelog — Strategic Flow Rewrite

Standard plan users just got 2.67x more API credits. Here is what changed — and what it unlocks.

Ahrefs

Product Updates · May 2026

API · Brand Radar · Analytics

Product Update · API · May 2026

Your API limits just changed. Significantly.

Standard plan users now get 2.67x more credits and up to 10x more rows per request. Advanced plans scale even further. This is not a minor quality-of-life update — it changes what you can build, automate, and analyse without hitting a wall.

2.67x

more API credits on Standard plans

10x

more rows per request on Standard plans

284K

SEOs and marketers reading the Ahrefs Digest weekly

AI platforms tracked in Brand Radar simultaneously

Review your plan limits → See API documentation

MAJOR UPDATE

28 April — API limits

More data, same plan. The ceiling just moved.

Lite, Standard, and Advanced plans all got increased API credits and row limits this month. The practical effect: workflows that previously required Enterprise-level access — large-scale keyword pulls, bulk backlink analysis, automated rank tracking across thousands of URLs — are now within reach on Standard. If you have scripts or pipelines hitting the old limits, they will run further without additional cost.

MAJOR UPDATE

Brand Radar — AI visibility across 5 platforms

ChatGPT, Perplexity, Gemini, Copilot, Grok. Your brand in all of them.

Brand Radar now tracks brand mentions and citations across every major AI platform — including Grok, added 24 April. For each platform, you get mentions, impressions, citations, and AI Share of Voice. The data goes back five months on ChatGPT and Perplexity, three on Gemini and Copilot. If your buyers are asking AI assistants who to use, this is where you find out what they are being told.

MINOR UPDATES

Everything else this month

Three smaller changes worth knowing about.

GSC Insights now shows average position of the highest-ranking URL per keyword — useful when multiple pages compete for the same term. Web Analytics groups traffic by acquisition channel including LLM and Newsletter, not just Search and Direct. AI Content Helper added a Chat function for improving content structure and topical depth without leaving the editor.

Next step

Check your current plan limits before building around the old ones.

If you have automated workflows or reporting pipelines using the Ahrefs API, the new limits may already affect what you can pull. Review what your plan now supports before your next build cycle.

Review your plan limits →

❌ Before

Title: Ahrefs Changelog: Running List of New Features

A filing label. Tells the reader what the page is, not what changed or why it matters. An SEO scanning their inbox has no reason to open it.

✅ After

Title: Standard plan users just got 2.67x more API credits. Here is what changed — and what it unlocks.

Names the reader, names the number, names the consequence. The reader who has ever hit an API limit recognises their situation immediately.

The 6 upgrades — and why they work

1 · Title leads with the reader's outcome, not the content type

The original announces that this page is a changelog. The rebuild announces that something changed that affects the reader directly. "Standard plan users just got 2.67x more API credits" is a fact that creates immediate relevance — anyone on Standard who uses the API needs to read this. The original gives them no reason to.

2 · 2.67x and 10x elevated from prose to stat cards

The original buries both numbers mid-paragraph. They are the most operationally significant data points in the entire update — they determine what workflows are now possible — and they have no visual prominence. The rebuild makes them the first thing the reader sees above the fold. Numbers that change what users can build should never appear in a sentence.

3 · Major vs minor hierarchy introduced

The original gives identical visual treatment to a 10x API increase and a new metric in GSC Insights. The rebuild separates them explicitly: MAJOR UPDATE badges on the API and Brand Radar changes, MINOR UPDATES for everything else. The reader can now scan and immediately understand what requires their attention this month.

4 · Consequence named before feature description

The original API entry opens with "We've massively increased API limits" — feature first. The rebuild opens with the operational consequence: "workflows that previously required Enterprise-level access are now within reach on Standard." The reader understands the business implication before processing the technical detail.

5 · Brand Radar rebuilt as a single coherent section, not 12 scattered entries

The original changelog has Brand Radar updates spread across eight months with no consolidation. A reader trying to understand what Brand Radar now is has to reconstruct it from fragments. The rebuild presents Brand Radar as a complete capability — five platforms, five months of history, AI Share of Voice — in one section that lands as a product decision, not a list of patches.

6 · CTA connected to the update's consequence

"View all plans" in the original has no logical link to the changelog content. The rebuild closes with "Check your current plan limits before building around the old ones" — a direct consequence of the API update. The action follows naturally from what the reader just learned, instead of appearing as a disconnected commercial insert.

This is the Strategic Flow method

Consequence before feature. Numbers as architecture, not prose. Hierarchy that tells the reader what matters before they have to decide. Every section answers the silent question — "does this affect me, and what should I do?" — before asking them to act. Visit strategicflow.carrd.co to get started.

    Failure patterns identified in this teardown

    Filing Label Subject  · 
    Feature-First Bias  · 
    Missing Hierarchy  · 
    Consequence-After-Caveat  · 
    Zero Social Proof  · 
    Generic Urgency Theatre
  