builder.io
Paid content
Categories: Artificial Intelligence
One codebase for engineers, designers, PMs, and marketers. Everyone works from one source of truth, on brand and in code, with no handoffs to clean up.
Related questions
More questions →How Do Marketers Use Ahrefs for SEO and Content Research? A Beginner's Walkthrough
Ahrefs is a data platform that helps marketers see what people search for, which pages rank for those searches, and who links to those pages. If you're new to it, the fastest way to learn is to start from a real task rather than browsing menus. This walkthrough uses one common goal — finding content and keyword opportunities for a site — and shows the exact steps, which reports to open, how to read the columns, and how to turn the data into a shortlist of tasks.
The steps below describe the general workflow of the platform. Exact menu labels, limits, and available features can change between plans and over time, so treat the interface as the source of truth and check the in-product help or documentation when a term is unfamiliar.
Step 1: Define the goal before opening any tool
Ahrefs answers questions, so the quality of your output depends on the quality of your question. Write down one sentence before you start. Examples:
- "I want 20 keyword ideas for a beginner's guide to home coffee brewing."
- "I want to know which pages on my site have lost the most traffic in the last 6 months."
- "I want to find sites that link to my competitors but not to me."
Each of these maps to a different report. Marketers who skip this step usually end up staring at a dashboard full of numbers with no decision to make.
Step 2: Enter a domain or a keyword
Most workflows begin in one of two places:
- Site Explorer — enter a domain or URL. Use this when your question is about a specific website (yours or a competitor's).
- Keywords Explorer — enter a keyword or phrase. Use this when your question is about a topic or search demand.
A practical habit: start with the competitor or topic you already know is relevant, then expand. If you sell running shoes, entering a well-known running retailer's domain will surface far more useful structure than entering a generic term like "shoes."
Step 3: Read the main columns without over-trusting them
Reports share a common set of columns. Learn what each one actually measures:
| Column | What it tells you | How beginners misread it |
|---|---|---|
| Volume | Estimated monthly searches for a keyword | Treating it as exact traffic you will get |
| Keyword Difficulty (KD) | How hard it looks to rank in the top results | Assuming a low KD guarantees a ranking |
| Traffic / Traffic Potential | Estimated visits a page or keyword can bring | Confusing page-level and keyword-level numbers |
| Referring Domains | Number of unique domains linking to a page | Counting total backlinks instead of unique domains |
| DR / UR | Domain and URL rating on a 0–100 scale | Comparing scores across unrelated niches |
Two rules of thumb: volume is an estimate, not a promise, and difficulty is a relative signal, not a gate. A keyword with modest volume and low difficulty that exactly matches your offer usually beats a high-volume term you cannot realistically rank for.
Step 4: Filter and sort to surface opportunities
Raw lists are noise. Filters turn them into a to-do list. Useful starting filters:
- Keyword Difficulty: cap it at a level your site can realistically compete for. A new site should start low; an established site can raise the ceiling.
- Volume: set a floor so you ignore terms nobody searches.
- Include / exclude words: remove branded terms, job listings, or irrelevant modifiers.
- Search intent: separate informational, commercial, and transactional queries so you don't write a blog post for a page that needs a product listing.
Then sort by the metric that matches your goal — traffic potential for content planning, referring domains for link building, or traffic decline for audits.
Step 5: Turn findings into a shortlist
A report is only useful once it becomes a list of tasks. A simple template you can copy:
Opportunity | Target keyword | Intent | Est. volume | KD | Page to create/update | Owner | Status
Fill it with 10–20 rows, not 200. For each row, decide one of three actions:
- Create a new page for a keyword gap you can serve.
- Update an existing page that already ranks but underperforms.
- Ignore it, with a one-line reason, so you don't revisit it next month.
This is where most beginners stall: they collect data but never commit to a decision. Forcing a create/update/ignore choice per row fixes that.
Step 6: Common beginner mistakes
- Chasing volume only. A high-volume keyword with the wrong intent sends traffic that never converts.
- Ignoring search intent. Check what actually ranks before deciding what to publish.
- Comparing DR across niches. A DR 40 in one industry is not equivalent to DR 40 in another.
- Treating estimates as facts. All third-party search data is modeled, not measured.
- Skipping the audit loop. Research is not a one-time event; revisit your shortlist and check whether the pages you built actually moved.
Where to get help with terms and metrics
Ahrefs maintains an in-product help center and a glossary of SEO terms, and the platform links to documentation from most reports. When a metric is unclear, open the help entry for that specific term rather than guessing — misreading one column can distort an entire content plan.
A realistic first session
If you have one hour, do this: pick one competitor, open Site Explorer, sort their top pages by traffic, filter to pages relevant to your offer, and write down five topics you could cover better. Then open Keywords Explorer for one of those topics, apply a difficulty and volume filter, and add three supporting keywords. You now have a shortlist of eight items and a clear next action — which is the actual point of using Ahrefs as a marketer.
Website Overview
An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality. Page metadata, canonical configuration and social previews work together to provide more consistent search and sharing presentation.
Domain and Registration
Registered in 2013, this domain has about 13 years of history. That suggests continuity, although ownership and purpose may have changed. Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The registrar is NameCheap, Inc., a widely used domain service provider. The domain uses the common .io extension, which is not an independent safety signal.
DNS and Email
The lowest TTL is 60 seconds, supporting rapid record changes at the cost of more frequent lookups. Nameservers are provided by Namecheap, indicating managed DNS hosting. DNS and provider evidence indicate traffic passes through the Amazon CloudFront CDN, which may support caching and traffic distribution. MX records point to the Google Workspace email service. The CNAME points to d2z9noecspqfwq.cloudfront.net, associated with Amazon CloudFront.
TLS and Certificates
The certificate uses an RSA 2048-bit public key, offering broad client compatibility. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued within the Amazon cloud or CDN ecosystem. The certificate is valid for about 197 days in total, with 110 days remaining.
HTTP and Browser Security
X-Powered-By exposes backend information: Express. The response lacks these common security headers: HSTS, CSP, X-Content-Type-Options, Referrer-Policy, Permissions-Policy. CORS permits any origin to read this response. This is common for public resources; sensitive responses need narrower handling. The x-cache, via response header indicates a CDN or caching proxy in the delivery path. No obvious internal addresses or debug information were found in the headers.
Technology Stack Analysis
The public page identifies Google Tag Manager, Amazon CloudFront, Express without precise versions, leaving fewer clues for version-specific scanning.
Search and Social Sharing
Twitter Card metadata is configured. The title has 58 characters, within a common display range. A meta description is present, with 151 characters. The observed directives allow indexing and link following. No Generator meta tag is publicly exposed.
Hosting and Email
Pages, Search and Sharing
| Meta description | One codebase for engineers, designers, PMs, and marketers. Everyone works from one source of truth, on brand and in code, with no handoffs to clean up. |
|---|---|
| Canonical URL | https://www.builder.io/ |
| Language | English (default) |
| Twitter Card | summary_large_image |
Social Sharing Preview
13 fieldsrobots.txt (opens in a new tab)
8 rulesAll bots 0 allowed · 8 disallowed
/content//apps//app//models//admin/account//spaces/o/
No matching rules.
Sitemaps
1
Registration details RDAP / WHOIS
| Registrar | NameCheap, Inc. |
|---|---|
| Registered | 2013-05-19 |
| Expires | 2027-05-19 |
| Domain status | clientTransferProhibited https://icann.org/epp#clientTransferProhibited |
| Nameservers | dns1.registrar-servers.com、dns2.registrar-servers.com |
| DNSSEC | unsigned |
DNS records
| Type | Name | Value | TTL | Priority |
|---|---|---|---|---|
| A | d2z9noecspqfwq.cloudfront.net | 108.138.64.16 | 60 | — |
| A | d2z9noecspqfwq.cloudfront.net | 108.138.64.47 | 60 | — |
| A | d2z9noecspqfwq.cloudfront.net | 108.138.64.71 | 60 | — |
| A | d2z9noecspqfwq.cloudfront.net | 108.138.64.75 | 60 | — |
| AAAA | d2z9noecspqfwq.cloudfront.net | 2600:9000:2508:1400:1b:cf6f:280:93a1 | 60 | — |
| AAAA | d2z9noecspqfwq.cloudfront.net | 2600:9000:2508:5600:1b:cf6f:280:93a1 | 60 | — |
| AAAA | d2z9noecspqfwq.cloudfront.net | 2600:9000:2508:6000:1b:cf6f:280:93a1 | 60 | — |
| AAAA | d2z9noecspqfwq.cloudfront.net | 2600:9000:2508:8200:1b:cf6f:280:93a1 | 60 | — |
| AAAA | d2z9noecspqfwq.cloudfront.net | 2600:9000:2508:9800:1b:cf6f:280:93a1 | 60 | — |
| AAAA | d2z9noecspqfwq.cloudfront.net | 2600:9000:2508:a200:1b:cf6f:280:93a1 | 60 | — |
| AAAA | d2z9noecspqfwq.cloudfront.net | 2600:9000:2508:b000:1b:cf6f:280:93a1 | 60 | — |
| AAAA | d2z9noecspqfwq.cloudfront.net | 2600:9000:2508:c400:1b:cf6f:280:93a1 | 60 | — |
| MX | builder.io | aspmx.l.google.com | 1799 | 1 |
| MX | builder.io | alt1.aspmx.l.google.com | 1799 | 5 |
| MX | builder.io | alt2.aspmx.l.google.com | 1799 | 5 |
| MX | builder.io | alt3.aspmx.l.google.com | 1799 | 10 |
| MX | builder.io | alt4.aspmx.l.google.com | 1799 | 10 |
| NS | builder.io | dns1.registrar-servers.com | 1800 | — |
| NS | builder.io | dns2.registrar-servers.com | 1800 | — |
| TXT | builder.io | MS=85674A50BC5FB9F985C2BCDA1E774EB4DB4FD424 | 1799 | — |
| TXT | builder.io | MS=ms38839399 | 1799 | — |
| TXT | builder.io | ZOOM_verify_nrT26zsj7qDbcKRHGdaopC | 1799 | — |
| TXT | builder.io | anthropic-domain-verification-ch5mfv=htAoNe8L7J56TqrIO6oyxylYT | 1799 | — |
| TXT | builder.io | apple-domain-verification=qfl0WUzxdWxQ5sJL | 1799 | — |
| TXT | builder.io | coda-verification=4d4da3b9-ad9e-4a8e-a463-d4f9d93770ad | 1799 | — |
| TXT | builder.io | docusign=0dcfe40d-d88b-4054-9249-4efd2420fc2e | 1799 | — |
| TXT | builder.io | firebase=builder-3b0a2 | 1799 | — |
| TXT | builder.io | google-site-verification=-BTh4v7FtxG6n7VGYSWp-7_m0ZNpd5NTT31i14y6jSE | 1799 | — |
| TXT | builder.io | google-site-verification=kCrO1SXgXo074JYPYPZzEcSMBA-Tw3tEZlfaW42CbCU | 1799 | — |
| TXT | builder.io | google-site-verification=kccSB4aB2uVuPyy9nFDRB0vPcIXm1SDaHHr52oCz7-g | 1799 | — |
| TXT | builder.io | google-site-verification=plGLufpD3qqejcxbf0COWScDMpVQMyYLiVezcv9S0F4 | 1799 | — |
| TXT | builder.io | google-site-verification=xBNkc4ppaqNYXOd_85XSg2s2InXq9P-DDAUibkXlt7c | 1799 | — |
| TXT | builder.io | v=spf1 include:_spf.firebasemail.com include:5149643.spf10.hubspotemail.net ~all | 1799 | — |
| CNAME | www.builder.io | d2z9noecspqfwq.cloudfront.net | 1799 | — |
| DMARC | _dmarc.builder.io | v=DMARC1;p=quarantine;rua=mailto:[email protected],mailto:[email protected],mailto:[email protected]; ruf=mailto:[email protected]; fo=1; sp=quarantine; | 1799 | — |
TLS and certificates
| Assessment | Normal configuration |
|---|---|
| Supported protocols | TLSv1.2、TLSv1.3 |
| Negotiated protocol | TLSv1.3 |
| Certificate subject | *.builder.io |
| Issuer | Amazon |
| Valid until | 2027-01-12T23:59 · Remaining when checked: 110 days |
| Verification details | Certificate trust: Passed · Hostname match: Passed |
HTTP response headers
| Header | Value |
|---|---|
| content-type | text/html |
| cache-control | public, max-age=5, stale-while-revalidate=86400, stale-if-error=2628000 |
| server | Google Frontend |
| x-frame-options | SAMEORIGIN |
| access-control-allow-origin | * |
User reviews (0)