Nexscope

Pages Websites

Resource Affected Pages MCP

Find which pages on a website are affected by a broken or slow resource. Call the Resource Affected Pages API via REST or MCP to automate SEO research.

CostEstimated 10 credits / callOnline Test

Resource Affected Pages AI Prompts & Use Cases

After connecting this MCP tool to your AI assistant, you can ask the questions below. Replace bracketed placeholders with your own inputs and use the supported values in Arguments.

New to Nexscope MCP? Follow the connection guide, then use the prompts below. The Integration and Parameters & Response tabs contain the connection steps, call example, and technical reference.

1. Find Pages Using A Resource

Prompt: Find pages using [resource URL] in my completed website audit [audit reference]. Show the affected pages so I can assess the scope of a resource issue. Return up to 10 results in this request.

2. Review A Smaller Result Sample

Prompt: Find pages using [resource URL] in my completed website audit [audit reference]. Show the affected pages so I can assess the scope of a resource issue. Limit the review to [number of results, at most 10] and identify whether the returned sample is incomplete.

3. Prioritize Affected Pages With Failures

Prompt: Find pages using [resource URL] in my completed website audit [audit reference]. Show the affected pages so I can assess the scope of a resource issue. Return up to 10 results in this request. Among the returned affected pages, identify broken pages and HTTP error checks, retaining page URL, status and the shared resource URL. Do not claim the resource caused every page issue.

What You Need to Provide

Provide the existing reference returned by the corresponding source request, from your own account. A placeholder reference cannot retrieve a real result.

Missing values are not zero. Interpret only returned evidence within its observation period and sample scope.