newsharecounts

Link UnfurlerPurpose·Link previewSafety·SafeSEO impact·HighBlocked by·Not yet measuredSnapshot·2026-04

01 /Overview

newsharecounts is a single-page fetcher with no publicly identified operator. It fetches one page (or a small set) when triggered by a user action, typically a link being shared on social media, a messaging app, or an RSS reader.

Volume tracks shares and clicks rather than crawl schedules. A trending link can produce a sudden spike, but newsharecounts will not crawl the rest of your site.

Blocking it usually means the link previews on the corresponding platform stop showing your title, image, and description.

See newsharecounts on your own site

02 /Identification

Match the User-Agent header on incoming requests against the pattern below.

regex

newsharecounts

For higher confidence, also verify the source IP against the operator's published ranges. UA strings can be spoofed; IP ownership is harder to fake.

03 /Control

The polite way is a robots.txt rule. Compliant agents respect it; the others ignore it.

robots.txt

User-agent: newsharecounts Disallow: /

Test a URL

Paste any URL on your site and we'll fetch its robots.txt to check whether newsharecounts is allowed.

04 /Technical fingerprint

Renders JavaScript

IP verification

User-Agent only

Crawl frequency

Per user action

Honors robots.txt

Yes

Honors Crawl-delay

Varies

05 /Expected behavior

Expect one-off requests triggered by user actions like sharing a link or adding a feed. Volume tracks engagement on the host platform.

Common questions

Should I let newsharecounts through?

In most cases, yes. Fetchers power link previews and feed readers. Blocking breaks the user experience on social and messaging platforms. If volume gets noisy, rate-limit it before you block it outright.

Does blocking newsharecounts affect my Google rankings?

No. newsharecounts is not a search-engine crawler. Your ranking on Google or Bing is unaffected by what you do here.

How do I confirm a request is really from newsharecounts?

Look at the User-Agent header in your access logs and match it against the strings listed above. Worth knowing that the User-Agent is easy to fake, so this check tells you "the traffic claims to be newsharecounts", not "the traffic is genuinely newsharecounts". If you need stronger guarantees, look for a reverse-DNS check or wait for the operator to publish IP ranges.

What breaks if I block newsharecounts?

Link previews, embeds, and unfurls on whatever surface newsharecounts feeds will stop rendering. Users sharing your URLs into that platform will see a bare link instead of a rich card. Usually that's the first thing people regret blocking.

Why can't I tell who operates newsharecounts?

Some bots run under generic User-Agent strings or are operated by smaller, less-documented companies. The pragmatic default is to treat unverified operators as untrusted traffic. If volume climbs, log the source IPs and check whether they cluster around a single network or ASN. That'll usually surface who's actually behind it.

What's the cleanest way to control newsharecounts?

Two layers. Robots.txt for the polite crawlers that read it, and rules at your CDN or edge for the ones that don't. Rankly's Agent Experience handles both from a single config, so you can allow, block, rate-limit, or serve a stripped-down version per bot. Agent Analytics handles the observation half so you know which bots are actually worth a rule.

Agent Directory

newsharecounts

Link UnfurlerPurpose·Link previewSafety·SafeSEO impact·HighBlocked by·Not yet measuredSnapshot·2026-04

01 /Overview

Volume tracks shares and clicks rather than crawl schedules. A trending link can produce a sudden spike, but newsharecounts will not crawl the rest of your site.

Blocking it usually means the link previews on the corresponding platform stop showing your title, image, and description.

See newsharecounts on your own site

02 /Identification

Match the User-Agent header on incoming requests against the pattern below.

regex

newsharecounts

For higher confidence, also verify the source IP against the operator's published ranges. UA strings can be spoofed; IP ownership is harder to fake.

03 /Control

The polite way is a robots.txt rule. Compliant agents respect it; the others ignore it.

robots.txt

User-agent: newsharecounts Disallow: /

Test a URL

Paste any URL on your site and we'll fetch its robots.txt to check whether newsharecounts is allowed.

04 /Technical fingerprint

Renders JavaScript

IP verification

User-Agent only

Crawl frequency

Per user action

Honors robots.txt

Yes

Honors Crawl-delay

Varies

05 /Expected behavior

Expect one-off requests triggered by user actions like sharing a link or adding a feed. Volume tracks engagement on the host platform.

Common questions

Should I let newsharecounts through?

Does blocking newsharecounts affect my Google rankings?

No. newsharecounts is not a search-engine crawler. Your ranking on Google or Bing is unaffected by what you do here.