Google Apps Script Parasite SEO: Complete Guide

Google Apps Script lets you publish a web app on script.google.com. Some people use these pages for parasite SEO. Parasite SEO puts content on another site's domain. The publisher hopes that the host site's reputation will help the page rank.

This tutorial shows you how to run a small test. You will create a page, review it, publish it and track the result. The test does not use cloaking. Each visitor and crawler gets the same page.

This guide focuses on the practical workflow. For the data, examples and full analysis, read our original investigation: Spammers Are Using Google Apps Script to Rank in Google Search.

Use this for research and education. Google can remove the page or suspend the account. Use a separate Google account. Do not use a client or third-party brand without written consent. Follow Google's spam policies and Apps Script terms.

How the method works

Google Apps Script is a tool for Google Workspace. It can automate products such as Sheets, Docs and Gmail. It can also publish a script as a public web app. Google gives that app a URL which ends in /exec.

Our research found Apps Script pages for Gemini API keys, crypto referral codes, money-making guides and medical searches. Some pages showed Google an article but sent a person to an offer. This is cloaking, and it breaks Google's spam rules. The launch kit blocks common cloaking patterns.

What you'll learn

In this tutorial you will learn how to launch your own Apps Script site using our launch kit that we've used for our own experiment. You will learn 3 styles of websites that have shown to work in our research and you can see the live samples here:

• Fullkitch Journal: guide site

• Fullkitch: product landing page

• Top 3 AI restaurant stock management tools: article

What the video test found

> Our test showing that the App Script site can rank #1 for low difficulty keywords like this.

In our internal test, Google started to show pages on day two. One page reached position 7. A page for a harder term reached page four.

These results show that the pages can appear in search. They do not show that every page will rank. Rankings can change or disappear at any time.

Read the full Google Apps Script investigation for the evidence and limits.

Before you start

You need:

• Node.js and npm.

• Git.

• A separate Google account.

• A coding agent, such as Codex or Claude Code.

• The Apps Script Launch Kit.

• CLASP, the command-line tool for Apps Script.

• agent-browser if you want the coding agent to read your site style.

• An indexing service such as Agent Mole if you want to repeat the video workflow.

1. Install the tools

Install CLASP:

npm install -g clasp

Install agent-browser only if the coding agent must read an existing site:

npm install -g agent-browser
agent-browser install

Clone the launch kit:

git clone https://github.com/Synscribe/apps-script-launch-kit.git
cd apps-script-launch-kit

2. Connect your Google account

Sign in to the separate Google account. Open the Apps Script settings. Turn Google Apps Script API on.

Then run:

clasp login

A Google page will open. Sign in and allow access. CLASP can now create and update Apps Script projects from your computer.

3. Create the pages

The launch kit supports the three page types shown in the video:

1. A small guide site with several pages.

2. A single product landing page.

3. A single blog article or comparison page.

You only need one type for a real test. The video creates all three so that you can compare them.

Open the repository in your coding agent. For Claude Code, run:

claude --dangerously-skip-permissions

For Codex, run:

codex --yolo

These flags let the agent run commands without asking you first. Run the agent only inside the launch-kit folder. Use the separate Google account for deployment.

Then use a prompt like this:

Use this repository to create three sample sites for <your product URL>.

1. Create a small guide site about <topic>.
2. Create a single landing page for <product>.
3. Create a single comparison article for <keyword>.

The agent will install the project packages, create the sites and start the local previews. If you did not install agent-browser, the agent can use the default theme.

4. Review the local preview

The agent will give you a local URL for each site. Open each URL in your browser.

Read every page before you publish it. Check these items:

• The page answers the target search query.

• Each fact, price and comparison is correct.

• The page does not contain fake reviews or results.

• Each button goes to the correct page.

• Each product link has UTM tags.

• The disclosure is easy to find.

• A phone user can read and use the page.

Remove weak or false content. Ask the agent to make the changes. Do not publish until you approve every page.

5. Publish to Google Apps Script

After you approve the pages, give the agent this prompt:

Publish the approved sites to Google Apps Script.
Give me the public /a/viral/ URL for each live page.
Open each URL in a private browser session and confirm that it works without a Google sign-in.

The Apps Script editor and CLASP usually show this short URL:

https://script.google.com/macros/s/<deployment-id>/exec

For this test, use the /a/viral/ form:

https://script.google.com/a/viral/macros/s/<deployment-id>/exec

The deployment ID stays the same. The launch kit uses the /a/viral/ form in its page links and sitemap. This is also the form that we saw in Google Search.

Use one URL form for the full test. Do not submit the /dev URL. It works only for the project owner. Do not copy the temporary script.googleusercontent.com URL after a redirect.

6. Ask Google to discover the pages

Publishing a page does not make Google index it. You also cannot verify script.google.com in Google Search Console because you do not own the domain.

The video uses IndexInstantly:

1. Copy each public /a/viral/ URL from the coding agent.

2. Keep the full query string for each page, such as ?page=<page-name>.

3. Paste the URLs into a new IndexInstantly job.

4. Check that every URL contains /a/viral/.

5. Submit the job.

This step does not guarantee indexing or ranking. IndexInstantly does not publish enough evidence to prove how its discovery method works. You can instead link to the test pages from a page that Google already crawls.

7. Measure the test

Check the pages once a day for at least seven days. Record:

• Whether Google indexed each page.

• The position for the target keyword.

• Clicks from the utm_source=apps-script links.

• The date when a page appears, moves or disappears.

Search for the full deployment ID to check both public URL forms. Also search for the exact page title and the target keyword.

> Simply search for your deployment URL, you are testing if it’s indexed. After it’s indexed, try searching for your keyword to see if it ranked for your target keyword

For a better test, publish the same page on a domain that you own. Keep the content and links the same. Compare which version Google finds and ranks first.

Stop the test if Google sends an account warning, removes the page or shows a manual action.

Live examples

• Fullkitch Journal: guide site

• Fullkitch: product landing page

• Top 3 AI restaurant stock management tools: article

Resources

• Apps Script Launch Kit

• Full investigation: how people use Google Apps Script for parasite SEO

• CLASP

• agent-browser

• Agent Mole