--- title: "Find AI Queries in Google Search Console · GSC PAP" source: https://gscpap.com/guides/ai-queries-in-google-search-console updated: 2026-10-25 --- [All guides](https://gscpap.com/guides) Guide · about 14 minutes # AI queries in Google Search Console: how to tell people, AI Mode and agents apart By the [GSC PAP team](https://gscpap.com/about) · Updated October 25, 2026 Search Console has never said where a query came from, and for years it didn't need to: a query was something a person typed into Google. In 2026 the same report also holds follow-up questions from AI Mode conversations, searches an AI assistant ran on someone's behalf, and the odd script. They all arrive as plain rows in the Queries table. We sorted every query our own site received between May 2 and October 21, 2026 into five groups by their shape. This guide shows what each group looks like, with real examples, the regex filters that find them, what they do to your CTR and average position, and where the same visits show up in Google Analytics 4. Every number here comes from gscpap.com, our own property, so you can follow the method end to end before running it on yours. One caution before the numbers. Our site is about AI tools for SEO, a topic AI assistants research all the time, so we see more agent activity than most sites will. The method carries over; the percentages won't. ## Does Search Console show AI queries? Yes, but without labels. Google's John Mueller has said that Search Console includes AI Overviews and AI Mode in the general Performance report, and that someone who asks a follow-up question in AI Mode is "essentially performing a new query", with that response's impressions, position and clicks counted against the new query. Nothing in the report marks which rows those are. Searches made by other AI assistants can appear too. When an assistant runs a Google search to answer someone, your page can earn an impression from it like from any other search. In November 2025 this became hard to miss, when whole ChatGPT prompts began showing up as queries in some sites' reports; OpenAI said it had fixed a glitch affecting a small number of searches. A search an assistant runs through a different engine never reaches Search Console at all. The generative AI performance reports Google began rolling out in June 2026 break AI visibility down by page, country, device and date, but not by query. So the query text is still the only place to look, and reading it means inferring where a query came from by its shape. Nothing below is a label Google provides. It is pattern matching you can check row by row. ## Five kinds of searcher in one query report Sorted by shape, the queries on our site fell into five groups. The examples are verbatim from our report. | Group | What it looks like | Example from gscpap.com | Who is behind it | | --- | --- | --- | --- | | Short keyword queries | One to five words: a topic, maybe a modifier | google search console historical data | Mostly people searching the classic way | | Long natural-language queries | Six or more words that read like a sentence or a spoken question | what is the difference between ga4 sessions and gsc clicks | People typing full questions, or the opening question of an AI Mode conversation. The two look the same | | Conversational follow-ups | Means nothing without the turns before it; no topic word at all | there must be a way | A follow-up inside an AI Mode conversation, which Google counts as a query of its own | | Agent-written queries | Instructions, templates, fragments of documents, rephrased variants ending in "official" | which tools detect cannibalization across posts and suggest which article to merge or redirect? explain how recommendations are generated. | An AI assistant searching Google to complete a task for its user | | Automated queries | Numbered queries, placeholders, code identifiers, search operators | 12161: how to track keywords | Scripts: test sets run through a search tool, scrapers, index checks | The groups are defined by the regex patterns further down, applied from the bottom of this table up: automated first, then agent-written, then follow-ups, then word count. ## What the five groups looked like on our own site Search Console names only part of a site's queries, and only named queries can be classified. On our site, between May 2 and October 21, 2026, the named queries covered 37% of impressions and about 2% of clicks. Nearly every click came from a query Search Console does not show, and that is worth keeping in mind through everything that follows. Within the named queries, the groups split like this: | Group | Share of named queries | Share of named impressions | Median position | Queries in the top 10 | | --- | --- | --- | --- | --- | | Short keyword queries | 64% | 48.1% | 58 | 12% | | Long natural-language queries | 15% | 43.2% | 79 | 6% | | Conversational follow-ups | 1% | 0.1% | 4 | 100% | | Agent-written queries | 12% | 6.2% | 23 | 42% | | Automated queries | 8% | 2.5% | 18 | 25% | gscpap.com, Search Console API, web search, May 2 to October 21, 2026. Median position is the median of each query's average position. Agent-written queries, share of named impressions by month - May: 0.6% - June: 4.9% - July: 4.7% - August: 6.6% - September: 11.3% - October: 7.8% gscpap.com, Search Console API. May starts on the 2nd, October ends on the 21st. - Agent-written queries were 6.2% of named impressions over the whole period, and their share grew: under 1% in May, about 5% in June and July, 7% in August, 11% in September and 8% in the first three weeks of October. - They ranked far better than everything else. 42% of agent-written queries showed our page in the top 10, against 12% of short queries. A query with five requirements in it matches very few pages, and one specific guide is often the best of them. - Every conversational follow-up ranked 3 or 4, and one of them produced a click. - Agent-written and automated queries together were 8.7% of named impressions, and earned no clicks at all. ## Conversational follow-ups: queries with no topic in them These queries on our site contain no word about Search Console, analytics or SEO. Each one still showed one of our pages near the top. | Query | Position | Page it showed | | --- | --- | --- | | there must be a way | 4 | Our guide to anonymized queries in Search Console | | is it free to use? | 3 | Our FAQ on whether GSC PAP is free | | i want to do it for free | 4 | Our home page | gscpap.com, Search Console API, May 2 to October 21, 2026. - Google could only have matched these to our pages using the earlier turns of a conversation. That fits Mueller's description of AI Mode, where a follow-up is a new query that carries the conversation with it. - "there must be a way" reads like a reply to being told that anonymized queries can't be recovered, which is exactly what the page it surfaced explains. - You can't target these words, and shouldn't try. What they tell you is which page ended up answering a conversation. Treat them as a signal about that page, not as keywords. - Most follow-ups are probably too rare for Google to name, so the few you can see are a floor, not a count. ## Agent-written queries: what an AI searching for its user looks like These are the clearest sign of an assistant at work: queries no person would type, because they still carry the machinery of the task. On our site they came in five recognizable shapes. | Shape | Example from gscpap.com | What gives it away | | --- | --- | --- | | Prompt scaffolding | context: location: united states (not for language). do not include location references in your response. question: which is more reliable for finding cannibalization ... | Instructions meant for the model were sent as the search | | Research briefs | compare options that merge ga and gsc to map keywords to landing pages and reclaim hidden traffic drivers, and show what connectors are required. | A whole task with deliverables, phrased as an instruction | | Rephrased bursts | google search console performance report data retention 16 months official | Six reorderings of the same words, each with "official" added, on 15 days between June 5 and July 2 | | Working documents | keyword,category,current position,previous position,position trend,last 3mo clicks ... | A spreadsheet header, searched on 36 days between July 15 and October 20 | | Plan headings | b. quick wins ... gsc striking distance (already ranking positions 11-30, snapshot 2026-07-13) | An outline heading with a fixed snapshot date, searched on 42 days between August 26 and October 21 | Examples ending in ... or containing ... are shortened; the rest are verbatim. - None of the agent-written queries produced a click. An agent reads the results and fetches what it needs instead of clicking through like a person, so these queries add impressions without adding visits. - The repeats are worth noticing. A heading with a fixed snapshot date, searched on 42 different days, looks like a scheduled agent rerunning the same research. Somewhere there is likely a recurring report about striking-distance keywords whose research step keeps landing on our quick wins guide. - Read them as briefs. The research brief above is a spec for a page: combine GA4 and Search Console, map keywords to landing pages, list the connectors required. It showed our anonymized queries guide at position 6, which covers only the hidden traffic. Our guide that joins Search Console and GA4 page by page did not appear, and at the time it did not compare the ways to combine the two or say what each one needs. In October 2026 we added that section to it. - When a page does answer every clause, it wins. The cannibalization question in the first table ranked our cannibalization guide at position 1. ## Automated queries: test sets, scrapers and index checks The last group is neither people nor AI assistants. These queries come from scripts, and they look like it. - Numbered queries: "12161: how to track keywords", "12197: keyword rank change", "15627: keyword tracking" and five more with five-digit prefixes, all about rank tracking, on and off from May to October. That is a numbered list of questions being run through a search tool, most likely an evaluation or test set. - Placeholders: "keyword2692" and "keyword-papsbzvc", the kind of value a template fills in before anyone replaces it. - Dataset names: "gooaq?" shares its name with GooAQ, a public research dataset of questions collected from Google. - Footprints: "gsc-cursor-current-page" and "gsc.page" are a class name and a URL fragment from Google's Programmable Search element. Searching for them finds sites that embed it, and we matched on the letters gsc. - Index checks: site: searches, from people or tools checking what Google has indexed. - Exclude this group from CTR, position and keyword research. It tells you nothing about demand. ## Regex filters that find each group in Search Console In Search Console, open Performance, then Search results, add a Query filter, choose Custom (regex) and paste one of the patterns below. The filter uses RE2 syntax and matches anywhere in the query unless you anchor it with ^ or $. Queries in the report are lowercase, and so are the patterns. Apply them in order, because they overlap: a sentence an agent wrote can start with "no " and look like a follow-up. Mark automated queries first, then agent-written ones, then follow-ups, and sort whatever is left into long and short by word count. We tested every pattern against the Search Console API on October 25, 2026. ### 1\. Automated queries Numbered queries, placeholders, dataset names, search operators and quoted code identifiers. Add the footprints you find on your own site. ```regex (^\d{3,6}: |^keyword[-0-9]|gooaq|^(site|inurl|intitle):|"[a-z]+-[a-z-]+") ``` ### 2\. Agent-written queries Prompt scaffolding, instructions, "official" added to a query, outline numbering, comma-separated lists and site: operators written with a dot. It catches the shapes we saw; extend it with the ones you see. ```regex (context:|question:|do not include|explain how|compare options|\bofficial\b|snapshot \d{4}|^[a-z]\. |[a-z],[a-z]|^site\.) ``` ### 3\. Conversational follow-ups Queries that open the way a reply does. Expect false positives, such as product names that start with "it", and read the matches before you count them. ```regex ^(i |i'm |im |is it |there |yes|no |ok |can you |what about |and |but |it |this |that ) ``` ### 4\. Long natural-language queries Six words or more. Change the 5 to 9 for ten words or more, a common cutoff for conversational searches. ```regex ^(\S+\s+){5,}\S+$ ``` - To get a group's share, compare its filtered totals with the totals for a filter that matches every query, such as .\*, not with the unfiltered totals. Any query filter drops anonymized queries, so the unfiltered total is the wrong denominator. - The patterns describe shapes, not origins. Read the matches before you report a number. - In the Search Analytics API, the same patterns go into a dimension filter with the includingRegex operator. [![Search Console Query filter dialog set to Custom (regex) with a pattern that matches queries of six words or more](https://gscpap.com/images/guides/ai-queries-in-google-search-console.webp)](https://gscpap.com/images/guides/ai-queries-in-google-search-console.webp) Add a Query filter, choose Custom (regex) (1) and paste a pattern (2), here pattern 4 for six words or more. ## What these queries do to your CTR and average position Each group pulls your averages in a different direction, so a site with a growing share of AI-shaped queries can watch its metrics move while nothing changes for the people who visit. - CTR falls. Agent-written and automated queries earn impressions and almost never clicks. On our site they were 8.7% of named impressions with no clicks at all. Take them out before you compare CTR across months. - Average position improves on paper. Agent-written queries ranked well (a median of 23, against 58 for short queries), so they pull the average up while bringing no visitors. - Impressions grow without visits. When impressions rise and clicks stay flat, check how much of the rise comes from these two groups before blaming titles or AI Overviews. - The visible part is a floor. Long, unique questions are exactly the ones Google anonymizes. On our site, named queries covered 37% of impressions and about 2% of clicks, so any share you measure from named queries understates how much AI-shaped searching reaches you. ## The rest of the trail: server logs and GA4 An impression in Search Console is only the first footprint an AI answer leaves. When an assistant decides to read your page, its fetcher requests the page from your server. When the person reading the answer clicks the source link, Google Analytics records a visit. Each footprint lives in a different tool, and none of them sees the whole trail. | Where | What it records | What it misses | | --- | --- | --- | | Search Console | Google searches that showed your page, including AI Mode and agents searching Google | Searches made through other engines, and most long, rare queries, which are anonymized | | Server or CDN logs | Fetches by AI user agents: ChatGPT-User and OAI-SearchBot (OpenAI), Claude-User and Claude-SearchBot (Anthropic), Perplexity-User and PerplexityBot (Perplexity) | The question that triggered the fetch, and whether anyone read the answer | | Google Analytics 4 | People who clicked through from an assistant, in the AI Assistant channel | Bot fetches, which never run the tracking script, and visits that arrive without a referrer | Training crawlers such as GPTBot and ClaudeBot show up in logs too. They collect pages for model training, not to answer a particular question. ## How many visits AI assistants send, measured in GA4 In May 2026 Google Analytics added an AI Assistant channel to the default channel group. When a session's referrer is a recognized assistant, GA4 sets the medium to ai-assistant and files the session under that channel, with no setup. On our property it changed the picture fast. From April 28 to October 24, 2026, AI assistants sent almost as many sessions as Google organic search. From October 1 to 24 they sent nearly four times as many. | Assistant | Share of assistant sessions | Filed under AI Assistant | | --- | --- | --- | | ChatGPT | 58% | 82% | | Claude | 38% | 100% | | Perplexity and Gemini | 4% | 67% | | All assistants | 100% | 88% | gscpap.com and app.gscpap.com share one GA4 property. April 28 to October 24, 2026. - The channel caught 88% of assistant sessions. The ones it missed were ChatGPT sessions from May, before the channel existed, which stayed under Referral and Unassigned, and Perplexity sessions that arrived with a utm_source but no medium. Search sessionSource for chatgpt, perplexity, claude, gemini and copilot to find yours. - Clicks from AI Overviews and AI Mode come from Google's own results page, so they sit in Organic Search with everything else, not in AI Assistant. Search Console is the only place they can be told apart, and only by the shape of the query. - Assistant visitors arrived closer to signing up. They landed on our home page, the sign-in page, the setup guide for Claude connectors and the pricing page, while Google organic visitors landed on the home page and the guides. 58% of assistant sessions were engaged against 56% from Google organic, with 2.4 pages per session against 1.4. ## What to do with AI queries in your Search Console data None of this needs new tracking. It needs a monthly habit and a few changes to how you read the reports. - Measure the groups every month. Run the four filters, write down impressions and clicks per group, and watch the agent-written line. It is the most direct evidence that assistants are researching your topic. - Report CTR and position without the automated and agent-written groups, and say in the report that you did. - Read agent-written queries as briefs. Each one lists what an assistant was asked to find. Check which of your pages it showed and whether that page answers every clause. If it answers half, that is the page to extend. - Write for the requirements, not only the keyword. The queries that ranked us highest carried requirements: which tool, how its recommendations are generated, what connectors are needed. Pages that state how something is computed, what it requires and how the options compare are the ones that match. - Don't chase the wording of follow-ups. Improve the page the conversation landed on. - Check that your CDN or bot protection isn't blocking the fetchers you want. Some security settings block AI agents by default, and an assistant that can't fetch your page answers without it. - Look at the landing pages of AI Assistant sessions in GA4. They show which of your pages assistants cite when they send someone your way. ## Limits of this method Shape-based classification is useful, and it is easy to overstate. Keep these in view when you report on it. - It is inference. Search Console doesn't record where a query came from. The groups describe shapes, and some people write long, formal queries too. - It sees only named queries. Most long and unique queries are anonymized, so every share here is a share of what Google chose to name. - One site is not a benchmark. Ours is about AI tools for SEO, which assistants research constantly. Expect the method to transfer and the percentages not to. - The patterns will age. Agents change how they search, so when the shapes in your report change, update the patterns. - Queries can contain other people's words. In 2025 some leaked prompts in Search Console included personal details. We quote only queries without personal or company information, and shortened three of them. ## Classifying your own queries with Claude The prompt works in any client connected to GSC PAP. Not set up in Claude yet? [Connect GSC PAP to Claude](https://gscpap.com/integrations/claude-ai-connectors) ### The scenario Your impressions have climbed for three months while clicks stayed flat, and CTR keeps slipping. Before rewriting titles, you want to know how much of the rise comes from queries no person typed, and whether assistants are already sending you visitors. ### The prompt ```prompt Use the gsc-pap MCP. For sc-domain:example.com, last 90 days: 1) Call search_analytics_query with dimensions ["query"] and row_limit 25000, paging with start_row until a page comes back empty. 2) Classify every query in this order. Automated if it matches (^\d{3,6}: |^keyword[-0-9]|gooaq|^(site|inurl|intitle):|"[a-z]+-[a-z-]+"). Agent-written if it matches (context:|question:|do not include|explain how|compare options|\bofficial\b|snapshot \d{4}|^[a-z]\. |[a-z],[a-z]|^site\.). Follow-up if it matches ^(i |i'm |im |is it |there |yes|no |ok |can you |what about |and |but |it |this |that ). Long if it has six or more words. Short otherwise. 3) For each group, report queries, impressions, clicks, CTR, impression-weighted position and share of named impressions, with the ten biggest queries. 4) Call get_performance_overview for the same range and tell me what share of total impressions and clicks the named queries cover. 5) Call list_ga4_properties, find this site's property, then call ga4_traffic_sources with dimension "channel" and again with "source". Report AI Assistant sessions, and any chatgpt, perplexity, claude, gemini or copilot sessions filed under another channel. ``` ### What happens 1. #### Claude pulls every named query search_analytics_query returns up to 25,000 query rows per call, and Claude keeps paging until Google has nothing left. The Performance report would have stopped at 1,000. 2. #### Claude sorts them into five groups The patterns run in order, so a sentence an agent wrote is never counted as a follow-up just because it starts with "no". Claude lists the matches per group, which is where you catch a false positive. 3. #### Claude measures what each group does to your numbers Impressions, clicks, CTR and position per group show whether the CTR drop sits in the agent-written and automated groups or in the queries people type. 4. #### Claude puts the named share in context get_performance_overview returns the property's total, anonymized queries included. The share of it that named queries cover tells you how much of the picture the classification can see. 5. #### Claude checks the visits The AI Assistant channel in GA4 shows the visits assistants sent. Claude then looks for assistant referrers under Referral and Unassigned, which the channel doesn't catch. ### Outcome You get a monthly breakdown of your Search Console queries by who most likely made them, a CTR and position you can compare across months without agents and scripts mixed in, and the number of visits AI assistants actually sent. If the agent-written group is growing, you also get the list of briefs assistants are researching on your topic. ### Where to take it next - Ask for the agent-written queries with dimensions \["query", "page"\] to see which page each one showed, and whether that page answers every part of the brief. - Run the same classification on the 90 days before and compare the agent-written share. - Ask for GA4 landing pages filtered to the AI Assistant channel to see which pages assistants send people to. - Report branded queries separately before you classify, so your own name doesn't blur the short and long groups. ## Frequently asked questions ### Can Search Console tell me which queries came from AI? No. Search Console has no field for where a query came from. AI Mode and AI Overviews are counted in the standard Performance report as ordinary queries, and searches other assistants run on Google look like any other search. You can only infer the origin from the shape of the query, which is what this guide does. ### Are AI Mode searches included in Search Console? Yes. Google has said AI Mode is included in the general Performance report, and that a follow-up question in AI Mode counts as a new query with its own impressions, position and clicks. The generative AI reports Google began rolling out in June 2026 don't include query data. ### Why do AI agent queries get impressions but no clicks? An agent reads the results and fetches the pages it needs directly. It doesn't click through the results page the way a person does, so the search counts as an impression for your page, and the visit, if there is one, shows up as a bot request in your server logs rather than as a click. ### Do ChatGPT searches show up in Search Console? Some searches AI assistants make show up as Google searches, and in 2025 whole ChatGPT prompts appeared as queries on some sites until OpenAI fixed what it called a glitch. A query in your report doesn't tell you which assistant made it, and searches an assistant runs through another search engine never reach Search Console. ### How do I see ChatGPT traffic in Google Analytics 4? Use the AI Assistant channel in the default channel group, which GA4 added in May 2026. Then search sessionSource for chatgpt under Referral and Unassigned: sessions from before the channel existed, and visits tagged with a utm_source but no medium, stay outside it. ### Should I exclude AI queries from my SEO reports? Exclude automated queries everywhere, and report agent-written queries separately. Keep them in your keyword research, though: an agent-written query is a precise description of what someone asked an assistant to find. ## Other guides [All guides](https://gscpap.com/guides) [ ### Good position, no clicks: find the SERP features eating your CTR Ranking third and getting no clicks usually means something sits above you: an AI Overview, a featured snippet or a map pack. How to check which, query by query. 7 min read ](https://gscpap.com/guides/low-ctr-at-good-position-serp-features)[ ### Find the pages quietly losing organic traffic, before the rankings go Content decay is slow enough to miss on a dashboard. How to find the pages whose clicks keep sliding, tell decay from seasonality, and decide what to refresh. 7 min read ](https://gscpap.com/guides/find-pages-losing-organic-traffic)[ ### Traffic changed: how to compare two Search Console periods and find out why Clicks are down 18% and nobody knows why. How to compare two periods properly, avoid the three traps that fake a drop, and find the queries and pages behind it. 7 min read ](https://gscpap.com/guides/compare-search-console-date-ranges)[ ### Google Search Console anonymized queries: measure the traffic you can't see Search Console hides anonymized queries from query rows but counts them in totals. Learn what they are, why no tool reveals them, and how to measure them. 6 min read ](https://gscpap.com/guides/google-search-console-anonymized-queries)[ ### GSC clicks vs GA4 sessions: why they differ and how to tie clicks to conversions A Search Console click and a GA4 session measure different things. Why the numbers never match, what gap is normal, and how to compare and combine them page by page. 11 min read ](https://gscpap.com/guides/correlate-organic-clicks-to-ga4-conversions)[ ### Audit Core Web Vitals across your site with AI Audit Core Web Vitals with Claude through a hosted PageSpeed Insights MCP server: Lighthouse lab data and real-user CrUX field data for your top pages. 7 min read ](https://gscpap.com/guides/audit-core-web-vitals-with-ai)[ ### Google Search Console historical data: how to keep it past 16 months Google Search Console keeps 16 months of historical data, then deletes it. Here is what it includes and how to keep it longer, from BigQuery to an archive. 8 min read ](https://gscpap.com/guides/recover-search-console-history-past-16-months)[ ### Build a weekly SEO health report with Claude Automate a weekly SEO report with Claude: one saved prompt pulls Search Console changes, quick wins, decaying pages, GA4 conversions and Core Web Vitals. 8 min read ](https://gscpap.com/guides/weekly-seo-health-report-via-claude)[ ### Bulk URL inspection in Google Search Console: diagnose indexing issues at scale Search Console inspects one URL at a time. The URL Inspection API allows 2,000 checks a day per property. How to inspect in bulk and find indexing issues. 8 min read ](https://gscpap.com/guides/diagnose-indexing-issues-bulk-url-inspection)[ ### Track keyword rankings in Google Search Console, past the 16-month limit See a keyword's position history in Google Search Console, what that average really measures, and how to keep ranking history past the 16-month limit. 6 min read ](https://gscpap.com/guides/track-keyword-rankings-over-years)[ ### How to find striking distance keywords in Google Search Console Striking distance keywords rank just off page one of Google. Find them in Search Console, pick the ones worth fixing, and learn what to change on the page. 8 min read ](https://gscpap.com/guides/find-seo-quick-wins)[ ### How to find keyword cannibalization in Google Search Console Check for keyword cannibalization in Google Search Console: find queries where your pages compete, judge whether it hurts, and fix the cases that do. 8 min read ](https://gscpap.com/guides/detect-keyword-cannibalization) ### Tools that automate this workflow The MCP exposes 36 tools across 9 categories. These are the ones most relevant to this page: - [search_analytics_query](https://gscpap.com/tools#search_analytics_query) · Run any Search Analytics query with full dimension and filter support, identical to what you'd hit the GSC API for, but inline in chat. - [get_performance_overview](https://gscpap.com/tools#get_performance_overview) · High-level performance snapshot for a site: clicks, impressions, CTR, position over the last N days. - [get_search_by_page_query](https://gscpap.com/tools#get_search_by_page_query) · Drill into a specific page to see which queries drive its traffic, impressions, and average position. - [ga4_traffic_sources](https://gscpap.com/tools#ga4_traffic_sources) · Acquisition breakdown by channel, source, medium, or campaign. Rows with sessions, active users, conversions per bucket. Choose the dimension to slice by. [Browse all 36 tools](https://gscpap.com/tools) ### Skip the GCP project. Just sign in. GSC PAP is hosted, free, and read-only. No service account JSON, no Python venv, no API keys. Sign in with Google, mint a bearer token, paste it into Claude / Cursor / Claude Code. About 60 seconds end to end. [Sign in with Google](https://app.gscpap.com/login) Read-only Search Console scope, revoke anytime Want a guide for a workflow we have not covered? Email [support@gscpap.com](mailto:support@gscpap.com).