Need Guest Posts or Backlinks?

Tell us what you need and we will send suitable publisher options.

PUBLISHER REVIEW WORKSPACE

Bulk DA PA Checker for Guest Post Site Review

Prepare your publisher list and review original Moz metrics

Have a spreadsheet of guest post sites to compare? Paste domains or website URLs, or preview a supported local TXT or CSV file. Prepare a reviewable list, request original Moz DA and PA for explicitly selected targets when the connection is available, and choose which candidates to add to a manual review request.

Use the list to explain which publishers you want assessed, which audience you need to reach and what evidence matters before you consider a placement.

Prepare lists locally. Check original Moz DA and PA when a licensed Moz API connection is configured and available. The metric check is a separate, explicit action with a selected-target preview, CAPTCHA and usage limits; preparing a list alone does not retrieve scores. The separate Domain Authority Checker remains another route for source-labelled authority measurements.

Prepare my domain list

Request a publisher review

List preparation in your browser · Original Moz measurements when connected · Explicit target scope · Reviewed request

Prepare a bulk domain list

Paste the websites you want reviewed, one entry per line by default. Standard HTTP and HTTPS URLs, uppercase scheme names and internationalized hostnames are parsed into an explicit target scope. Review the original entry, effective target, status and explanation before using a row.

Preparation runs locally. Check selected targets with Moz below when the site administrator has connected and enabled the API. Only a confirmed Moz check sends those targets for metrics; notes and campaign briefs are not sent to Moz. The separately reviewed enquiry handoff never submits the form. Also see the Domain Authority Checker.

Optional original Moz DA and PA

Local list preparation remains free and separate. Only your explicit verified metrics request sends reviewed targets to the configured Moz API. DA belongs to a domain and PA to the displayed page; they are not Google scores.

Setup required: add a Moz API token and confirm public usage in this plugin’s admin. No licensed metric request is enabled.

Domains or website URLs — paste a list into the workspace. Choose an input separator deliberately; the import preview lets you inspect how a file is interpreted.

Example input — these are sample addresses, not verified publishers.

example.com
another-publisher.com
https://www.example.org/

Choose the target you mean: Hostname mode retains www and subdomains by default. Registrable-domain mode uses the included Public Suffix List rules, including private suffixes. Exact-URL mode retains the normalized page path and query; it does not turn a homepage into an article. Original entries remain in the report.

Prepare list creates a local preparation report. This preparation action does not contact the candidate websites or request authority scores. Use the separate Moz check after selecting accepted targets and reviewing the actual provider-query scope.

Your prepared rows appear in the workspace after preparation. Accepted, duplicate and rejected rows retain their own explanations. Preparing an entry does not check its authority, availability or suitability.

“Prepared” is a preparation status, not a metric result. It means the entry was accepted under the displayed parsing and scope rules. It does not mean a provider returned a score, a website was reached or a publisher accepted your campaign.

Select candidates for a Moz check or a review request. Keep the original report, add local row notes where useful and choose the accepted targets to carry forward. A Moz request is limited to at most 25 selected targets per check; review the active allowance before continuing.

Preview the selected targets and your campaign brief, then explicitly choose to add them to the request form. The handoff appends the reviewed text rather than replacing an existing message. You still review and submit the separate form yourself; preparation and handoff never submit it.

Check the actual Moz query scope

Prepare as many local rows as the active preparation limits allow, then select at most 25 accepted targets, or the lower active Moz batch allowance. Review the provider-query preview before completing the CAPTCHA and selecting the separate Moz check. Hostname scope requests the homepage URL while preserving www and subdomains; registrable scope requests a domain; exact-URL scope requests the normalized page URL with fragments removed only from the provider query.

Keep the metric owner and missing values visible

The source label is Moz API. DA describes the returned root domain, and PA describes the returned page. Spam Score, linking-root-domain counts, supported external-page or link counts and a last-crawled date are shown only when a supported value is returned. Missing, failed or unavailable values remain labelled as such, not replaced with zero. These measurements are not Google ranking scores or a publisher-safety verdict.

Read the date and limits correctly

The report’s UTC retrieval time records the check, not a new crawl or live index refresh. If Moz supplies a crawl date, it is identified separately. Provider setup, account allowance and site-configured usage caps can limit a request; local preparation remains usable independently. No result guarantees rankings, publisher acceptance or a placement.

Clean the list before requesting evidence

Keep target scope explicit

Hostname is the default and keeps www and subdomains. Registrable-domain mode uses the included public and private suffix rules; it is not a promise of legal ownership or a provider’s metric scope. Exact-URL mode keeps the normalized path, query and fragment by default. Removing one leading www, fragments or the listed tracking parameters are explicit options, not silent cleanup. Inspect normalization notices before carrying a target forward.

Inspect every interpreted row

Keep the original input, effective target, source row, preparation scope, status and explanation together. The parser rejects unsupported schemes, credential-bearing URLs, IP addresses, malformed or reserved hosts and nonstandard ports. A syntactically valid unknown suffix is labelled with a warning in hostname and exact-URL modes; it is rejected in registrable mode, where a recognized suffix boundary is required. Bare and protocol-relative inputs assume HTTPS with a notice. Acceptance is syntactic: no DNS, HTTP reachability, Google index or publisher-safety check runs here.

Choose a deliberate duplicate rule

Group repeated effective targets, group by normalized hostname, or retain all entries without grouping. A duplicate is marked with the row it repeats. All original rows remain reviewable, including duplicates and rejected entries; grouping is not silent deletion.

Preview local files before using them

Import supported UTF-8 TXT or CSV from your own device. For CSV, review the header choice and selected target column in the preview. Files are read in the browser; this is not a spreadsheet-metric import, a crawler, or an XLSX/PDF decoder.

Take a labelled preparation report with you

Search and filter row statuses, sort deterministically and select the candidates you want. Add local row notes. Copy targets or export a local preparation CSV, JSON or TXT report with an explicit full-report, current-view or selected-row scope. CSV output protects user-supplied cells against spreadsheet formula interpretation. These preparation reports keep the original evidence and your notes. After a Moz check, separate metric CSV, JSON and TXT exports retain returned fields, source, target scope, retrieval time and missing-data status. A missing metric remains unavailable, not a fabricated score or a substituted zero.

Know the limits and the data boundary

The default preparation caps are 1,000 rows, 200,000 UTF-16 input units and 2,048 units per entry. UTF-8 file imports default to 1 MiB and downloadable output to 10 MiB. Check active limits: optional controls can be disabled and administrators may lower allowances. Local preparation does not automatically save your list, fetch the supplied sites or send a metric request. Only after you explicitly review and request a Moz check are the selected query targets sent through this site to Moz; unselected rows, local row notes and campaign-brief fields are not included in that provider request. Normal site loading still makes ordinary page requests. A separate, explicitly reviewed handoff passes selected targets and the brief to the surrounding page; submitting the separate form sends that request.

Example: preparation is not a score

With hostname scope and effective-target grouping, the shared preparation engine treats this example list as shown below. These sample addresses are not verified publishers. The uppercase URL is normalized without fetching it; a repeated effective target remains a duplicate row, while unsupported input stays visible as rejected.

Original entryEffective targetPreparation status
HTTPS://WWW.Example.COM/Study?utm_source=demo#readingwww.example.comaccepted
example.comexample.comaccepted
www.example.comwww.example.comduplicate — repeats row 1
news.example.com/Guidenews.example.comaccepted
ftp://example.comNot acceptedrejected
[email protected]Not acceptedrejected
https://127.0.0.1/Not acceptedrejected

The report retains 7 original rows: 3 accepted, 1 duplicate and 3 rejected. None of these statuses confirms DNS, reachability, publisher acceptance or authority. Exact-URL mode is a separate choice when the page path matters.

What this page helps you do

Organize publisher candidates

Bring a scattered list of domains or exact page URLs into a consistent starting format. Inspect rejected rows, choose the duplicate rule and keep the original entry beside the effective target. Article paths remain available in exact-URL mode.

Give the reviewer a useful brief

A domain list becomes more useful when it includes your target page, subject, audience, market and budget. These details help a reviewer distinguish a relevant publication from a website that merely has an appealing score.

Ask for evidence before discussing a placement

Specify the authority measurements, source dates and publisher details you need. Keep metric review, publisher availability and the final placement quote as separate questions.

Keep the decision connected to your audience

The purpose of the review is to find publishers that make sense for your content and readers. Authority metrics can support that decision, but they do not establish it on their own.

How to use the bulk DA PA review workflow

  1. Paste or preview your candidates. Start with the websites already in your shortlist, or import a supported UTF-8 TXT or CSV file. This page does not discover new sites across the internet.
  2. Prepare and inspect the list. Choose hostname, registrable-domain or exact-URL scope and a deliberate duplicate policy. Inspect the original entry, normalized target, row status and rejected-row reason.
  3. Select the candidates to carry forward. Add row notes, preview the selected targets and your brief, then explicitly append them to the separate request form. Exact-URL mode can retain existing article URLs for page-level review.
  4. Describe the campaign. Add the target page, topic and audience, market or language, budget and exclusions in the workspace brief or the separate form. The review preview shows the supplied brief before you add it to your message.
  5. Check the evidence you need. When the Moz connection is available, preview up to 25 selected accepted targets, complete the CAPTCHA and explicitly request Moz measurements within the displayed usage caps. Keep the metric owner, returned scope and retrieval time with the results. Ask separately which publisher terms or other evidence still need confirmation.
  6. Review the response before deciding. Consider relevance, visibility, editorial standards, price and placement conditions together.

Submitting a review request starts a conversation about your requirements. It does not confirm a publisher, authorize payment or approve publication.

DA, PA and DR answer different questions

Domain Authority and Page Authority are proprietary Moz metrics. This workspace requests those original measurements from the connected Moz API rather than calculating substitute DA or PA. DA relates to the root domain returned by Moz; PA relates to the page returned by Moz. Ahrefs Domain Rating is a separate measure from a separate provider, not a Moz value or a relabelled DA. Their numbers should retain their original names and sources.

MeasurementWhat it describesHow to use it in a publisher review
Moz Domain Authority — DAComparative authority of a domain on Moz’s scaleCompare publishers serving a similar topic and market
Moz Page Authority — PAComparative authority of a particular pageReview the exact existing article or resource URL
Ahrefs Domain Rating — DRRelative strength of a domain’s backlink profile in AhrefsAdd a separate, clearly sourced comparison
Moz Spam ScoreA provider signal that can prompt closer investigationExamine the underlying site and links before reaching a conclusion
Linking root domainsDistinct domains linking to the measured target in the provider’s indexDistinguish link breadth from repeated links on one site

A PA value for a homepage describes that homepage. It cannot be used as the PA of a proposed guest post that has not been published.

DA, PA and DR are third-party measurements, not Google’s own ranking scores. No authority threshold guarantees a useful placement, a safe backlink or an improvement in search rankings.

Review more than an authority score

A publisher can look strong in a metric report and still be a poor fit for your campaign. A useful review records the evidence behind the choice.

Review questionEvidence to request or inspect
Does the subject fit?Relevant categories, recent articles and a clear reason your topic belongs
Does the audience fit?Content language, target market and readership evidence where available
Is the website active?Recent publishing, working pages and current editorial information
Does it have search visibility?Current visibility evidence with its source, scope and date
Is the article environment suitable?Useful surrounding content, authorship, references and placement context
What are the commercial terms?Confirmed price, writing requirements, disclosure, link attributes and approval steps
What remains uncertain?Unavailable metrics, stale data, unconfirmed acceptance and unresolved review questions

For observable technical, editorial and link signals, use the Publisher Site Risk Review. Its flags help prioritize inspection; they do not establish a Google penalty.

Example: a better brief produces a better shortlist

Suppose you are planning an article about study skills for adult learners. You have several education publications, a general lifestyle site and a broad business blog in your list.

Sending only a preferred DA range leaves the reviewer guessing about the campaign. Add the audience, language, target page and proposed subject, and the review can consider which publications already cover learning, qualifications or career development.

The resulting question becomes specific: which candidates have a suitable editorial setting, current visibility and confirmed placement terms for this article?

A smaller specialist publication may deserve closer consideration than a larger unrelated website. The decision needs evidence about the campaign’s fit, rather than a score alone.

What to include in your review request

Use this brief when adding the prepared domains to the form:

Brief fieldWhat to provide
Target pageThe URL you want the article to reference
Topic and audienceWhat the article will explain and who should read it
Preferred marketCountry, language or regional audience requirements
Candidate publishersThe prepared domain list
Exact pagesExisting article URLs requiring page-level review
Metric preferencesWhich measurements you want reviewed, with acceptable evidence sources
BudgetPer-placement or campaign budget, and whether writing is included
Content needsSupplied article, writing request, length or editorial requirements
ExclusionsPublishers, categories or content types you want avoided
TimingYour preferred schedule, subject to confirmed publisher terms

If you need help organizing these details, use the Guest Posting Campaign Brief Template.

Continue with the question you need answered

Need licensed authority measurements?

This workspace can request original Moz measurements for a reviewed selection when its Moz connection is configured and available. The Domain Authority Checker also supports single and bulk input for up to 25 distinct targets. Each tool depends on an available configured provider; unavailable data stays unavailable.

Need catalogue matching?

Use the Bulk Publisher Availability Checker to match supplied domains against catalogue records for a reviewed request. A catalogue match still needs current publisher acceptance confirmed.

Need a campaign-based shortlist?

The Guest Post Site Finder compares inventory options with your campaign requirements. Its fit ranking helps organize review; it is not a Google SEO score.

Need an initial budget range?

Use the Guest Post Pricing Calculator for estimates based on comparable inventory cohorts. The final placement quote and writing cost need separate confirmation.

These tools answer different parts of publisher planning. Choose the next step that resolves your remaining question.

Frequently asked questions

Does this bulk DA PA checker show live Moz scores?

When its licensed Moz API connection is configured and available, this page can retrieve original Moz DA and PA for a reviewed selection. Prepare the list, select up to 25 accepted targets, complete the CAPTCHA and explicitly run the Moz check within the active usage caps. The report identifies Moz as the source, the requested and returned scope, and the retrieval time. Request time is not a promise that Moz crawled or updated its index at that moment. If setup, quota or data is unavailable, that state is explained; no substitute score is manufactured.

Is preparing the list free?

The browser-local preparation workspace can be used without a payment step or a personal API key. Moz metric checks are a separate operation that depends on this site’s configured licensed connection and displayed usage caps; the page does not promise an unlimited or free provider quota. Manual research, writing or a placement may involve a separate quote. Request the scope and price before approving paid work.

Can I paste full website URLs?

Yes. Standard HTTP and HTTPS URLs are supported, including uppercase scheme names. Hostname mode prepares the host; registrable-domain mode groups by the included suffix rules; exact-URL mode retains the normalized path, query and fragment locally. The separate Moz query preview shows the actual request: hostname mode checks the homepage URL while preserving www or subdomains; registrable mode uses Moz’s domain scope; exact-URL mode uses the page URL with its fragment removed for the provider request. PA is for the returned page, not an unpublished guest post.

Does the tool remove duplicates?

Yes, when you choose a duplicate policy. Group by the effective target or the normalized hostname, or choose no grouping. Duplicate rows remain in the evidence report and identify the retained row; they are not silently discarded. Syntactic acceptance does not prove that a website exists.

How many domains can I prepare?

The default local preparation allowance is 1,000 rows and 200,000 UTF-16 input units, with up to 2,048 units per entry. Supported UTF-8 TXT and CSV files are limited to 1 MiB by default. Administrators may lower these limits; check the active values beside the workspace. These are preparation limits, not metric-query allowances. Each explicitly submitted Moz check allows at most 25 selected targets and is subject to CAPTCHA, configured usage caps and provider availability.

What is a good DA for a guest post site?

There is no universal answer. Compare publishers with similar subjects and audiences, then assess current visibility, editorial fit and placement terms. A higher DA cannot compensate for an unsuitable topic or an article that serves no useful purpose.

Does a high DA mean the publisher is safe?

No. An authority score cannot verify a publisher’s editorial standards, establish a penalty status or guarantee the treatment of a link. Review the website and the proposed article separately.

Does the prepared list confirm publisher availability?

No. This page does not match the list against live inventory or obtain publisher acceptance. Request an availability review and confirm the terms before making a decision.

Can agencies use the tool for client campaigns?

Yes. Prepare a separate list and brief for each campaign. Search, status filters, stable sorting, row selection and notes help organize the review. Copy or export the labelled full preparation report, current view or selection in the implemented formats. When a Moz check was run, use its separate metric exports to retain the returned evidence and source labels. Row notes and campaign briefs are not sent in the Moz metric request. Account dashboards, saved projects, score history and automated report sharing are not included.

Can authority scores guarantee rankings?

No. They are comparative provider metrics. Rankings, indexing and traffic depend on many factors, and this review process does not guarantee those outcomes.

Request a reviewed publisher shortlist

Send your prepared domains, target page, audience and campaign requirements. Ask for the metric evidence, editorial fit and placement terms you need before approving a publisher.

For a campaign that includes authority preferences, explore High DA/DR Guest Posting Services alongside a review of relevance and current visibility.

Review your request details

Tell us which domains you are considering and what your article needs to achieve. Include exact page URLs where page-level review matters.

Review the populated details and use the separate form to request a review and quote. The workspace does not submit a request or change the existing form’s fields or submission controls.

Your request does not authorize payment or publication. Publisher acceptance, content requirements, pricing and link attributes need confirmation. Paid placements should use appropriate disclosure and link qualification.