Moz API V2 Link Status Endpoint Documentation – Help Hub – Moz

If the Links endpoint is the big fishing net, the Moz API V2 Link Status endpoint is the flashlight. It is the tool you use when you already have a suspected backlink source in mind and want to answer a very specific question: does Moz see this source linking to my target in its index? That sounds simple, but in SEO, simple questions often save entire afternoons, a few gray hairs, and at least one dramatic sigh in Slack.

This endpoint is especially useful for technical SEOs, link auditors, digital PR teams, competitive analysts, and developers building custom reporting tools. Instead of pulling a giant link list and then hunting through it like a detective in a crime show with poor office lighting, you can check many sources against one target in a focused, efficient way. In plain English, it helps you confirm whether a known page, domain, or root domain is recorded as linking to a page or site you care about.

What the Moz API V2 Link Status Endpoint Does

At its core, the Link Status endpoint is designed to return information about links from many sources to a single target. In the Moz API family, that makes it a precision tool rather than a bulk-discovery tool. You are not asking, “Show me all backlinks.” You are asking, “For these specific sources, what is the link relationship to this target?”

That difference matters. If you are checking whether a recently earned media mention is reflected in Moz’s index, validating outreach wins, confirming a partner link, reviewing a suspected lost backlink, or comparing how different sources point to a landing page, Link Status is the endpoint you reach for. It is also handy when you want to test one page versus another without running a broader backlink export.

In practical SEO workflows, this endpoint becomes a verification layer. You might use the Links endpoint for discovery, Linking Root Domains for broader domain-level insight, and Link Status when you want a yes-or-no-plus-context answer about specific sources you already know about.

Where It Fits in the Moz API V2 Ecosystem

Moz groups its links data endpoints under the V2 base URL, and Link Status sits alongside endpoints such as Links, Linking Root Domains, Link Intersect, Index Metadata, Final Redirect, and URL Metrics. That lineup tells you something important: Link Status is not supposed to do every job. It works best when paired with the rest of the toolkit.

Here is the easy way to think about it:

• Link Status checks whether known sources link to a single target.
• Links gives you lists of links pointing to a target.
• Linking Root Domains rolls things up at the root-domain level.
• Link Intersect helps with competitor gap analysis.
• Index Metadata helps you understand when the index changed.
• Final Redirect helps you avoid checking the wrong URL when redirects are involved.
• URL Metrics adds authority and link-related metrics for context.

So no, Link Status is not the loudest endpoint in the room. It is the one quietly doing accurate follow-up work while the bigger endpoints get all the attention. Classic middle-child energy.

Endpoint Basics: URL, Method, Format, and Authentication

The endpoint lives under the Moz Links API V2 base path and uses a POST request with a JSON body. Moz’s current setup materials also show a token-based header workflow for link-data calls, specifically using x-moz-token. That means your integration should be written cleanly and defensively: send properly structured JSON, set the correct headers, and never hard-code credentials in public code or client-side scripts.

Here is a simple, body-only example showing the shape developers commonly expect when discussing this endpoint:

That request structure is useful because it tells the story of the call in one glance. There is one target, many sources, and scope choices that determine how broadly Moz should interpret each side of the relationship. In other words, you are not just asking about a string of URLs. You are defining the level of the comparison.

Understanding target

The target is the page or site you want to evaluate. This could be a specific article URL, a subdomain, or a root domain, depending on how you define your scope. Choosing the right target is half the battle. If your live page redirects, canonicalizes elsewhere, or has tracking parameters hanging off it like holiday decorations in February, normalize it first.

Understanding sources

The sources are the places you want Moz to check. These can be specific pages or broader domains, again depending on scope. This is perfect for validating outreach campaigns, PR placements, directory entries, affiliate placements, or even internal quality checks when a team swears a link exists and your dashboard politely disagrees.

Understanding source_scope and target_scope

Scope is where good integrations become smart integrations. A page scope is narrow and exact. A root_domain scope is broader. If you set the wrong scope, you can create confusion fast. You may think a link disappeared when the real issue is that you checked the page level instead of the domain level, or vice versa. That is not a data problem. That is a “we asked the API the wrong question” problem.

Why SEOs and Developers Love This Endpoint

There are three big reasons the Link Status endpoint earns a spot in serious SEO tooling.

1. It validates specific backlinks fast

When a client says, “We got coverage on this site last week,” you do not always need a full backlink crawl. You need confirmation. Link Status lets you check targeted sources against the page or domain you care about. That speeds up reporting and keeps your outreach recaps grounded in actual indexed data.

2. It reduces noisy analysis

Bulk link exports are useful, but they can also become a junk drawer. When you only need to confirm a handful of relationships, Link Status gives you focused data instead of a kitchen sink full of unrelated link records.

3. It works beautifully in automation

This endpoint is a natural fit for scripts, dashboards, alerting systems, QA tools, and internal SEO products. If your team tracks earned links, partnership links, or high-value citations, you can build regular checks around Link Status and turn a manual verification task into a repeatable workflow.

Common Use Cases for the Moz API V2 Link Status Endpoint

Campaign verification

After a digital PR push, feed a list of placement sources into the endpoint and verify which ones point to your campaign URL, category page, or homepage.

Lost link monitoring

If a high-value link seems to have vanished, compare known sources against the target over time. Pair the results with Index Metadata so you can tell whether the issue is likely a true loss or just a matter of index freshness.

Redirect cleanup

If a campaign page moved, use Final Redirect first, then check Link Status against the final destination. That prevents the classic “the link is there, but we checked the retired URL” mistake.

Competitive validation

When you suspect an industry directory, review site, or niche publication links to competitors but not to you, Link Status gives you a more surgical way to confirm the relationship before escalating to a broader gap analysis.

Custom link QA in enterprise environments

Large sites often launch new templates, migrate directories, or update site architecture. Link Status can support spot checks when teams want to confirm that important sources still resolve to strategic targets after those changes.

What Makes a Good Link Status Workflow

The best workflow is not just “call endpoint, celebrate, go home.” It usually follows a cleaner sequence:

1. Normalize the target URL.
2. Check redirects if needed.
3. Choose scopes carefully.
4. Send a POST request with structured JSON.
5. Interpret the result in the context of index freshness.
6. Track usage because Link Status is a weighted endpoint.

That last point matters more than many teams realize. Moz pricing and usage are based on returned rows, and some endpoints are weighted. Link Status is one of them. Translation: if you get clever with volume but sloppy with planning, your quota can disappear like office donuts on a Monday morning.

Common Errors and How to Avoid Them

400 Bad Request

This usually means malformed JSON or invalid input parameters. Check your body shape, scope values, array formatting, and content type. A typo in a field name can ruin your afternoon with the efficiency of a dropped production table.

401 Unauthorized

This points to authentication problems, expired credentials, or plan-related limits. Re-check your token or credentials, confirm your account status, and verify that your authentication method matches Moz’s current documentation.

403 Forbidden

This can happen when the request uses an unsupported method or the account lacks permission. If you accidentally send a GET request to a POST endpoint, the API will not reward your optimism.

429 Too Many Requests

This is the API politely telling you to slow down. Add pacing, retry logic, and sane batching. In production integrations, exponential backoff is your friend. Treat it well.

ASCII-only URL errors

Moz’s help materials specifically mention ASCII-only URL issues. That is your cue to normalize and percent-encode URLs correctly. Non-ASCII characters, odd punctuation, and messy copied URLs can all produce preventable failures.

Best Practices for Better Results

Use crawlable, canonical targets

If the target page is not the version search engines and tools typically recognize, your analysis can get fuzzy. Use the clean canonical version where possible.

Pair Link Status with Index Metadata

Freshness matters. If a new backlink is not showing yet, the problem may be timing rather than absence. Index Metadata helps you understand whether Moz’s index has updated since the link went live.

Do not confuse page-level and domain-level checks

This is one of the easiest ways to misread results. Always decide whether the business question is about a specific URL, a subdomain, or a root domain before you set scope.

Batch thoughtfully

Because Link Status is focused and weighted, it is best used for curated source lists. Save your bulk-discovery hunger for other endpoints and reserve this one for verification, audits, and targeted checks.

Write documentation for your own team

Yes, really. Even if you are the only developer today, Future You is still a coworker, and Future You deserves notes about scopes, expected inputs, retry rules, and quota logic.

How to Explain This Endpoint to Non-Technical Stakeholders

If you need a client-friendly summary, try this: “The Moz API V2 Link Status endpoint checks whether Moz currently sees specific websites linking to a page or site we choose.” That is simple, accurate, and does not make anyone pretend to love JSON.

For marketing teams, that translates to confidence. It helps answer whether earned links are being recognized, whether important mentions are still live in the index, and whether outreach wins can be validated with a consistent process.

Real-World Experiences Using the Moz API V2 Link Status Endpoint

In real projects, the biggest lesson is that this endpoint shines when you already know what you are looking for. Teams often start by expecting it to behave like a complete backlink explorer, then realize its real superpower is verification. Once that clicks, the workflow gets dramatically better. Instead of dumping huge exports into spreadsheets and searching through them line by line, you can check a precise list of placements from outreach, partnerships, guest posts, directories, or press mentions and get a faster answer.

Another common experience is discovering that URL hygiene matters more than expected. A source may truly link to your content, but if your target uses tracking parameters, mixed casing, a redirecting version, or a slightly different path than the one you checked, your first result can look wrong. That is why experienced users usually clean the target first, confirm redirects, and only then run Link Status. It is less glamorous than “run script, become legend,” but it works.

Teams also learn pretty quickly that scope selection can change the story. A page-level check may say no, while a root-domain-level check may effectively say yes in the broader sense. That does not mean the API is inconsistent. It means the question changed. The most successful implementations make scope an explicit part of the reporting interface so nobody confuses page evidence with domain evidence.

On the operational side, quota awareness becomes a real-world issue once people begin automating checks. Because Link Status is a weighted endpoint, casual testing can quietly become expensive in row consumption. Mature teams usually solve this by checking only strategic sources, deduplicating lists before requests, and building usage monitoring into their scripts. That keeps the endpoint useful instead of turning it into the office version of leaving all the lights on.

One more practical lesson: Link Status works best when it is part of a sequence rather than a standalone ritual. The cleanest stacks often use Final Redirect to confirm the real destination, Link Status to verify specific sources, URL Metrics to add authority context, and Index Metadata to understand freshness. When those pieces are combined, you get a much more trustworthy picture of the link relationship. That is when the endpoint stops feeling like a tiny technical utility and starts acting like a reliable decision-making tool for SEO, product, and content teams alike.

Conclusion

The Moz API V2 Link Status endpoint is one of those tools that looks modest until you actually need it. Then suddenly it is the hero of the sprint. It gives developers and SEOs a focused way to verify whether known sources link to a single target in Moz’s index, and it does so in a structure that supports automation, audits, campaign validation, and smarter reporting.

If you use it with clean URLs, correct scopes, realistic expectations, and an eye on weighted usage, it becomes an excellent addition to a serious SEO stack. It may not be flashy, but neither is a seatbelt, and you still want one every time the road gets weird.