Seo Internal Link Map
Pricing
$0.01 / actor start
Seo Internal Link Map
Pricing
$0.01 / actor start
Rating
0.0
(0)
Developer
Eichan Jolly
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Features
Share
One job: collect unique <a href> links on one HTML page that point to the same hostname as the fetched page. Ideal for content editors, small-site owners, and SEOs reviewing on-page internal navigation.
For each target, the Actor keeps only the first anchor text and first link's rel=nofollow value. Internal links are not visited and are not tested for HTTP errors. External links and non-HTTP links are omitted.
Input
Just one input property, url (string): an HTTP(S) URL to a public HTML page.
{"url": "https://www.djangoproject.com/"}
This is also the prefilled example in input_schema.json. The URL was observed accessible without a redirect when checked on 2026-11-01. Public sites may change at any time. The sample is not a login-protected page.
Output
Output is written to the Apify default dataset (one JSON object per item), or to local storage/datasets/default/000000001.json, etc., when no Apify dataset ID is present.
{"sourceUrl": "http://127.0.0.1:46125/links","targetUrl": "http://127.0.0.1:46125/a","anchorText": "First link","isNofollow": true,"status": "ok","error": null}
This item is from the included local fixture, not a claim about the public input page. On a page with no internal anchors, a single record has targetUrl, anchorText, and isNofollow as null, status: "no_internal_links", and error: null.
How to run
- Use Python 3.12+; no packages need installing. From this folder, set
ACTOR_INPUT_JSONto the input JSON above and runpython src/main.py. - Alternatively, put the JSON in
storage/key_value_stores/default/INPUT.jsonand run the same command. - On Apify, the Actor reads
INPUTfrom the default key-value store using its provided ID andAPIFY_TOKEN, then POSTs the items to the default dataset; no Apify SDK is required. - For verification, run
python tests/test_actor.pyandpython tests/run_smoke.py. The latter launches a temporary local HTTP test server and captures the real script subprocess output and JSON undertests/evidence/.
Input priority: ACTOR_INPUT_JSON → APIFY_DEFAULT_KEY_VALUE_STORE_ID with authenticated Apify GET → local INPUT.json. There is no exact-match check against an APIFY_API_BASE_URL environment value; the standard https://api.apify.com endpoint is used directly.
Limits and safeguards
- One public HTML page only; at most 500 distinct same-host HTTP(S) targets. This is an on-page map, not a sitemap crawler.
- Different query strings and URL schemes are distinct links; fragments are removed. Anchor text is normalized whitespace.
isNofollowdescribes only the first anchor for a target, not all duplicates.same-hostuses the fetched page's hostname (not its registrable parent domain); ports are not filtered on extracted links. No targets are fetched.- Does not execute JavaScript, log into sites, use search-engine results, or fetch third-party website pages. No keys except Apify's own platform storage token.
- Honors robots.txt for the requested page and checked same-host redirects. A missing robots.txt (HTTP 404/410) is treated as no explicit restriction; other verification failures are returned as plain-language errors.
- Enforces HTTPS/HTTP, publicly routable DNS addresses, a 12-second timeout per request, up to 3 same-host redirects, and a 1.5 MB maximum HTML response. The server may impose its own rate limits.
- Script-mode tests use a temporary loopback-only test flag (
SEO_ACTOR_ALLOW_LOOPBACK=1) and local fixtures; production use should leave this flag unset. Live Apify deployment and Docker builds were not performed. - Errors are emitted as dataset items with stable null values and
status: "error", rather than Python tracebacks. If the dataset service is unavailable, a plain-language terminal error is printed.
Store suggestions (not configured)
Categories: SEO tools, Marketing, Developer tools. Suggested price: $0.01 per run. Store details are recorded in store_metadata.json. Nothing is published or billed automatically.