Google Sheets Apps Script Page Not Found? Causes and Fixes

If Google Sheets Apps Script says “page not found,” first check that you opened the script editor from the right Google account and from the spreadsheet that owns the script. The message can also point to an old or incorrect link, missing access, a deleted project, or a problem with a deployed web app; the fix depends on which page you were trying to open.

What “page not found” can mean

Apps Script is Google’s browser-based environment for creating scripts and add-ons, including scripts connected to Google Sheets. A page-not-found message is not specific enough to identify one cause by itself. It may appear when you open an editor link, a script project shared with you, or a web app URL created by a deployment. These are different destinations, so start by noting exactly what you clicked and whether the error page is on script.google.com or on a URL used by a web app.

A missing page is also different from a script that opens but fails while running. If the editor loads and shows an error in the execution log, that is usually a code, authorization, or service issue rather than a missing page. If Google instead says you need permission, that is an access problem. The wording and address-bar URL help narrow down what to try next.

Open the editor from the spreadsheet

For a script attached to a particular spreadsheet, open that spreadsheet in Google Sheets and choose Extensions > Apps Script. This is a reliable way to reach the spreadsheet’s bound script without relying on an old bookmark or a link copied from another account. If the Apps Script editor opens, the original error was likely tied to the route or link you used rather than the spreadsheet itself.

If the menu item is unavailable or the editor does not open, check that the file is actually open in Google Sheets, that you are signed in, and that you have permission to edit the spreadsheet. View-only access may not let you open or change its bound script. A copied spreadsheet can have its own separate bound script project, so opening the original file’s script link while working in a copy can be confusing.

You can also visit script.google.com and sign in to see Apps Script projects available to your account. This is useful for standalone projects, but it does not make every script visible: a project may belong to another account or may not have been shared with you. Prefer the spreadsheet’s Extensions menu when you know which sheet the script belongs to.

Check the Google account and project access

Google lets you sign in to more than one account in a browser. A spreadsheet may be open under one account while an Apps Script link is being opened under another. Look at the account avatar on both pages, then switch to the account that owns the spreadsheet or has been granted access. If the browser keeps selecting the wrong account, open a private or incognito window, sign in only to the intended account, and try the link again.

For a project shared by someone else, ask its owner to confirm that the project still exists and that your account has the needed access. A shared spreadsheet and its script are related, but access to one does not always answer every question about access to the other. The owner can check sharing settings and send a fresh link. Do not ask them to make a project public just to get past an error; granting only the access needed is safer.

If you owned the project, check whether it was moved, deleted, or created under a different Google account. A link to a file in Google Drive’s trash, or to a project that has been removed, will not work as an ordinary live project link. If you can still find the relevant spreadsheet, use its Extensions menu. If neither the project nor its owner can be located, Google support or an organization’s administrator may be needed to investigate account-specific access.

Know whether the script is bound or standalone

A bound script is associated with a Google file, such as a spreadsheet, and is commonly opened from that file’s Extensions > Apps Script menu. A standalone script is an independent Apps Script project that is not bound to a particular sheet. It can be opened from the Apps Script project list or through a valid project link. Confusing these types can lead to searching the wrong place or using an outdated URL.

Also distinguish the editor URL from a deployment URL. The editor is where authorized users view and change project code. A deployed web app has its own address for people to use, and it may have different access rules. If a link was shared as a way to run a tool, it may be the deployed app rather than the project editor. Ask the sender which one they intended you to open before changing project sharing settings.

If the missing page is a web app

A script project can exist and still have a web app link that no longer works. Deployments can be changed, replaced, or removed, and someone may have sent an old URL. Ask the project owner to check the current deployment in the Apps Script editor under Deploy > Manage deployments. For a new web app, the owner uses Deploy > New deployment, selects the web app type, reviews who the app runs as and who can access it, and completes the deployment process.

Apps Script web apps commonly provide an /exec URL for the deployed version. A development URL ending in /dev is for testing and is limited to users who can edit the script; it is not a general public link. A user who receives a development link without editor access may not be able to use it. A web app can also load but then show an authorization, sign-in, or application error, which is different from the deployment address itself being unavailable.

Changing who can access a deployment can expose data or allow actions under the account that runs the script. The owner should review the app’s purpose and the data it touches before changing access. If the app should be available only to people in an organization, its deployment settings and organization policy must allow that audience. If you are only an end user, request a current working link and the access level intended for you rather than trying to redeploy someone else’s project.

Consider Workspace settings and browser issues

In a work or school Google Workspace account, an administrator can control whether users may use Apps Script or related services. If the editor works with a personal account but not with the organization account, or several people in the same organization see the same restriction, ask the Workspace administrator whether Apps Script is available for your account and whether organizational rules affect the project or deployment. A user generally cannot override an administrator’s service settings from the browser.

Browser issues are worth checking after account and link problems. Reload the page, try a current supported browser, or open the URL in a private window to see whether an extension or stale sign-in session is interfering. If it works in a private window, review browser extensions and account sessions in the regular window. Clearing all browser data should not be the first step: it can sign you out of services and remove local site data without fixing a deleted project or missing permission.

Check the address carefully before retrying. A truncated link, an extra character, or a link copied from an email preview can send you somewhere different from the intended project. If the URL comes from a bookmark, message, or old document, ask for a fresh link. Avoid entering your Google password on a page reached through an unfamiliar redirect; sign in through Google’s normal sign-in flow and confirm the account shown.

A practical recovery order

Work through the simplest checks before making changes to a project. This helps avoid accidental edits or unnecessary changes to sharing and deployment settings.

Identify whether you are opening the editor, a shared project, or a deployed web app.
For a bound script, open the correct spreadsheet and choose Extensions > Apps Script.
Confirm the same Google account is active on the spreadsheet and Apps Script pages.
Ask the project owner to verify that the project exists, your account has access, and any web app link is current.
If the issue affects a managed account, ask its Workspace administrator about service availability or organization restrictions.
Try a private browser window or another browser only after checking the link and account.

Once the editor opens, avoid creating a replacement project until you know whether the original script contains important code or triggers. A new script does not restore an old project’s contents, settings, or deployment. If the spreadsheet is important, make a copy before making substantial changes, and ask the owner before editing a shared script that supports other people’s work.

Frequently Asked Questions

Why does Extensions > Apps Script say page not found?
Check that you opened the intended spreadsheet and are signed into an account with suitable access. If the same error persists, the project may have been removed, access may be restricted, or a Workspace administrator may have disabled Apps Script for your account.

Can I open a Google Sheets script directly?
Yes, if you have access to the project. For a script bound to a sheet, opening the sheet and choosing Extensions > Apps Script is usually the clearest route. Standalone projects can be opened from the Apps Script project list or a valid shared project link.

Why does an Apps Script web app link show page not found?
The link may be old, copied incorrectly, or associated with a deployment that is no longer available. Ask the owner for the current deployed URL and confirm that the deployment is intended to allow your account to use it. A development link is not a substitute for a general-use deployment.

Does page not found mean my script code is broken?
Not necessarily. If the editor page itself cannot load, the issue is more likely the link, account, project access, or service availability. Code problems normally appear after the editor opens and the script is run, often with details in the execution log.

Can a Workspace administrator block Apps Script?
Yes. Workspace administrators can manage access to services for users in their organization. If your account is managed and the problem appears organization-wide, contact the administrator rather than trying to change settings in the script project.

Should I make the script public to fix access?
No. Public access is not a general fix for a missing page and can create privacy or security risks. First confirm the correct account and link, then ask the owner to grant only the access needed for the project or deployment.

Try it: the Date Difference Calculator: days, months, years and weekdays between two dates, with the DATEDIF formulas.

More in How-to basics

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.