A writer opens a public guide in a browser and sees the article. A verified crawler can request the same address and get a challenge page from the web firewall. Both requests can look successful from a distance. Perplexity’s crawler guidance is a useful reason to check delivery before blaming a missing citation on the writing.
Trace one failed request
Collect the timestamp, requested path, response status and edge rule involved. Ask engineering to verify the claimed crawler against the provider's published guidance rather than trusting its name alone. Compare the response body with the public guide: a successful status carrying a browser challenge is different from the article being delivered.
Review the smallest relevant rule
If the block contradicts your policy, review the narrow exception with the site owner and verify a subsequent legitimate request. Retain the rule for protected paths. Close the access incident when the public content is served correctly. Whether the page is later used in an answer is a separate editorial measurement.
Close the right ticket
Hand engineering a specific URL, a time window and the expected first sentence of the guide. Once a verified crawler receives that text under the approved access policy, close the access ticket. If the buyer’s question still surfaces competitors, read their cited pages for evidence your guide lacks; reopening the firewall ticket will not answer that question.
