Skip to content
Good for Bots

Easy Payroll Calc

easypayrollcalc.com

Free calculator estimating employer payroll taxes and total cost of one U.S. hire

Click badge to copy

Changed your site? Run a new scan.

Claim to rescan

Claiming is free. Verify ownership to request a rescan after deploying your changes.

Unclaimed listings are checked automatically every 90 days.

Good for Bots report

Easy Payroll Calc scores 42 of 100: 42 of the 50 base points, none of the agent layer, no penalties.

Earned

42 of the 50 base points above the line, none of the agent layer below it.

42

3 prompts away

Copy them below ↓

34

Still open

Behind the checks below, with prompts in Pro.

24
Penalties0
How scoring works · current methodology →

Through a bot’s eyes

“Easy Payroll Calc is a free online employer payroll calculator that estimates the employer-side cost of one U.S. hire, including Social Security, Medicare, FUTA and state unemployment taxes, based on the homepage text.”

Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.

What it can read, and what stays hidden →

What a bot can read

The homepage text covers one subject: an employer payroll calculator for U.S. salary cost. It explains the inputs (pay, pay frequency and work state) and the taxes included: employer Social Security at 6.2% up to $184,500, Medicare at 1.45%, net FUTA at 0.6% on the first $7,000, and state SUTA. It also gives a table of 2026 new-employer SUTA rates and wage bases for the states and DC, plus FAQ answers on wage bases and on whether salary data is stored. The product's price is present as text, described as free. A contact email appears only in the JSON-LD Organization block, which also repeats the FAQ and gives the WebApplication offer as price 0 in USD. No Markdown version or llms.txt was supplied, so the JSON-LD adds only structured repetitions of homepage content. The calculator's own results are not in the text. Other calculator pages are referenced by link only, and their contents were not read.

What stays hidden

A model reading this input cannot learn what the calculator returns for any given salary, because results are not in the text. It cannot find the operator's name beyond Easy Payroll Calc, a postal address or support hours, and the only contact is an email address in structured data. It cannot tell which experience-rated or credit-reduction state rates apply to a specific employer, or what the linked state calculator pages contain.

What is Easy Payroll Calc?

S. salary cost.

Read more →

The calculator estimates the employer's cost of one hire by adding wages to employer Social Security, Medicare, FUTA and state unemployment (SUTA) taxes, with per-period and annual totals and wage-base flags. It is aimed at employers, including small businesses, and does not compute employee withholding or net pay. The homepage states that calculations run in the browser and that results are estimates, not tax, legal or accounting advice. It also lists 2026 federal and state planning rates and links to a payroll cost page and a payroll tax page.

3 prompts, 33 points

For Claude Code, Cursor or Codex. The score moves after the next scan.

+12.5score from 42 to 54

Serve Markdown at its own URL

No /llms-full.txt and no markdown versions linked from llms.txt.

Read prompt

+11.3score from 54 to 65

Publish a well-formed llms.txt

No /llms.txt on this site.

Read prompt

+10score from 65 to 75

Serve Markdown when asked for it

None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.

Read prompt

Pro

16 more prompts in Pro

Pro shows a prompt for every fix and drafts your llms.txt and robots.txt. It never changes the score.

$9 once, per listingSee Pro

Deployed your fixes? Rescan to update your score →

Ready-made files

Pro drafts these for this site.

Pro

A ready-made llms.txt and robots.txt

Pro drafts both files for Easy Payroll Calc from its scan, keeps only links and rules our parsers can verify, and hands them over ready to review and publish. It never changes the score.

See Pro

Select a check to see what we found and how it is graded.

Readable base

41.7 / 50

Passes.

3.3 of 3.3 points.

robots.txt is valid, with 1 user-agent group.

Passes.

8.3 of 8.3 points.

Sitemap declared in robots.txt, listing 17 URLs.

Fails.

0 of 8.3 points.

2 of 4 pages read pass. The page at /about publishes no structured data at all: no JSON-LD, no microdata, no RDFa.

Prompt in Pro →
Passes.

10 of 10 points.

All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.

Passes.

8.3 of 8.3 points.

5 of 5 assessed homepage navigation links expose usable destinations.

Passes.

4.2 of 4.2 points.

52 of 52 assessed homepage links and buttons have a nonempty accessible name.

Passes.

2.5 of 2.5 points.

6 of 6 assessed homepage form fields meet the static naming and field-semantics checks.

Passes.

2.5 of 2.5 points.

61 of 61 assessed homepage controls and role declarations meet the static role, state and relationship checks.

Passes.

1.7 of 1.7 points.

All 4 pages read pass. The homepage declares itself as its canonical URL.

Agent layer

0 / 50

Fails.

0 of 11.3 points.

No /llms.txt on this site.

Fails.

0 of 7.5 points.

No usable /llms.txt to judge.

Prompt in Pro →
Fails.

0 of 12.5 points.

No /llms-full.txt and no markdown versions linked from llms.txt.

Fails.

0 of 10 points.

None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.

Fails.

0 of 5 points.

robots.txt names no AI crawlers, so every operator has to guess.

Prompt in Pro →
Fails.

0 of 2.5 points.

No usage declaration found in robots.txt or the final successful homepage response header.

Prompt in Pro →

Penalties

− 0

Passes.

Penalty: 0 of 15 points.

Our crawler reaches the page without being challenged.

Passes.

Penalty: 0 of 20 points.

Nothing on the homepage tells a crawler to skip it or to withhold its snippet.

Passes.

Penalty: 0 of 25 points.

The captured homepage HTML contains 1069 content words; completeness is not assessed.

Passes.

Penalty: 0 of 25 points.

robots.txt allows every known search and user-fetch crawler to reach the homepage.

Passes.

Penalty: 0 of 10 points.

The homepage is served over HTTPS and returns HTTP 200.

Passes.

Penalty: 0 of 3 points.

The homepage provides both a non-empty title and meta description.

Passes.

Penalty: 0 of 3 points.

The homepage is reached in 0 redirects.

Passes.

Penalty: 0 of 3 points.

The homepage reached a plain crawler in 59 ms.

Agent capabilities

0 of 11 · no points

Each one found adds +1 to the badge.

Not applicable.

Adds +1 to the badge when found.

No API catalog published.

Not applicable.

Adds +1 to the badge when found.

No /auth.md published.

Not applicable.

Adds +1 to the badge when found.

No AI Catalog published, so no MCP server card can be discovered.

Not applicable.

Adds +1 to the badge when found.

No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No usable Agent Skills index was found at either well-known path or in the AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.

Not applicable.

Adds +1 to the badge when found.

No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.

Not applicable.

Adds +1 to the badge when found.

No HTTP 402 payment challenge on the homepage or robots.txt, and no manifest at /.well-known/x402.

Not applicable.

Adds +1 to the badge when found.

No ACP discovery declaration established at /.well-known/acp.json.

Not applicable.

Adds +1 to the badge when found.

No UCP discovery declaration established at /.well-known/ucp.

Not applicable.

Adds +1 to the badge when found.

No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.

Access & usage policy

Who can read this page, and for what purpose?

GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.

Sampled URL: https://easypayrollcalc.com/

Measured, our crawler
HTTP 200
GoodForBotsBot received HTTP 200 via a direct request.
Search and user-fetch crawlers refused
0 of 20
robots.txt refuses none of them.
Training crawlers refused
0
Refusing training would not change the score.

Crawlers and what robots.txt declares for them

Rules for the sampled URL, read the way RFC 9309 reads them. These are declarations, not access tests.

Crawlers and what robots.txt declares for them on the sampled URL
CrawlerPurposeDeclared accessScore effectRule that applies
Our crawler, measured
GoodForBotsBotGood for BotsSite diagnosticsFetchedHTTP 200, directNot scoredrobots.txt admitted our crawler
Search and AI answers
OAI-SearchBotOpenAIAI searchAllowedNoneNot named; User-agent: * applies
Claude-SearchBotAnthropicAI searchAllowedNoneNot named; User-agent: * applies
PerplexityBotPerplexityAI searchAllowedNoneNot named; User-agent: * applies
GooglebotGoogleSearchAllowedNot scoredNot named; User-agent: * applies
, all allowed
Fetches a person asked for
ChatGPT-UserOpenAIUser fetchAllowedNoneNot named; User-agent: * applies
Claude-UserAnthropicUser fetchAllowedNoneNot named; User-agent: * applies
Perplexity-UserPerplexityUser fetchAllowedNoneNot named; User-agent: * applies
, all allowed
Model training, never scored
GPTBotOpenAIAI trainingAllowedNoneNot named; User-agent: * applies
ClaudeBotAnthropicAI trainingAllowedNoneNot named; User-agent: * applies
Google-ExtendedGoogleAI training, GroundingAllowedNoneNot named; User-agent: * applies
, all allowed
Agents, extraction and others
, all allowed

The robots.txt groups behind this table

User-agent: *
Allow: /

https://easypayrollcalc.com/robots.txt

How to read this table

Each row says what robots.txt asks of that crawler. It does not show whether the crawler obeys, or how a firewall treats it. We measured only our own request.

Refusing search or user-fetch crawlers costs points under AI crawler access. Refusing training crawlers costs nothing.

Indexing directives, Content-Signal and AIPREF preferences are in the tabs below.

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access
  • Declared allow · Scan admission

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    The recorded robots admission decision allowed our crawler to proceed.

    GoodForBotsBot admission along the homepage request chain

    https://easypayrollcalc.com/

    robots.txt is present and valid

  • Observed · Direct request

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    Our request received HTTP 200. A status alone does not identify a WAF.

    Our recorded direct transport attempt; intermediate attempt URLs are not retained

    https://easypayrollcalc.com

    HTTP 200

    Serves the homepage over HTTPS with HTTP 200

  • Observed · Final homepage response

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    GoodForBotsBot received HTTP 200 via a direct request.

    homepage response

    https://easypayrollcalc.com/

    HTTP 200
    Transport: direct

    Serves the homepage over HTTPS with HTTP 200Serves our crawler without a challenge

Coverage and interpretation
  • Crawler coverage includes the registered identities and up to 50 user-agent entries from robots.txt. Source excerpts and detail groups are bounded; omissions are labelled.
  • Observed access describes GoodForBotsBot only. Other crawler entries describe declared rules, not tests of those operators' access.
  • Coverage is the sampled homepage response and collected robots.txt files. No indexing or citation is guaranteed. Usage preferences are declarations, not a legal determination of permission.
  • This explanation adds no points or penalties. Any score effects belong to the linked checks.
  • AIPREF and Content Signals keep their own definitions. AIPREF search can include processing used exclusively for search; training preferences are not a blanket ruling on every search process.

In its category

91st of 111 in SaaS & Web Apps

  1. 1Appnaryappnary.com
  2. 2BulkSharebulkshare.cloud
  3. 91Easy Payroll Calc · this reporteasypayrollcalc.com

The prompts above would take Easy Payroll Calc to 75, 19th in its category.

To the prompts ↑

Category average 58. The percentile appears once the catalogue holds a few hundred sites.

Scanned

Site profile

Login
Not established
API
Not established
Commerce
Not established

It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.

Scan details

Every scan is kept. Pro draws the history as a chart →

Scanned
13 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
126.4 KB
Took
12.7 s
Homepage
59 ms · direct
Pages read
4
robots.txt
allowed
Which pages the scan read

The homepage and up to three pages from the sitemap and homepage links. Structured data, page structure, Markdown negotiation and typed links check each page read and take the median page; other checks read the homepage.

  • Homepagealways read
  • /aboutabout · linked from the homepage · from the sitemap · read
  • /payroll-calculator/californialinked from the homepage · from the sitemap · read
  • /contactcontact · linked from the homepage · from the sitemap · read

More like Easy Payroll Calc:SaaS & Web AppsHR & RecruitingFinance & AccountingB2B

Same category

talhabashir.com

Free online calculators and tools for US taxes, mortgages, business and personal finance

Same category

vouchgeo.com

Tracks how AI assistants mention a brand across multi-question buying conversations

Also B2B

submityourstartup.now

Free weekly launch directory where early-stage founders list startups and are ranked by votes

interviewace.online

Real-time AI answer suggestions for job candidates during live video interviews

volanea.com

Transactional email, campaigns, and automation API with AI agent support