spotinst · RachelHooley · Feb 15, 2026 · Feb 15, 2026
diff --git a/add-noindex.ps1 b/add-noindex.ps1
@@ -0,0 +1,46 @@
+# Script to add noindex meta tag to all markdown files in src/docs
+
+$docsPath = "c:\repos-spot\help\src\docs"
+$metaTag = '<meta name="robots" content="noindex">'
+
+# Get all .md files recursively
+$mdFiles = Get-ChildItem -Path $docsPath -Filter "*.md" -Recurse
+
+$updatedCount = 0
+$skippedCount = 0
+$errorCount = 0
+
+Write-Host "Found $($mdFiles.Count) markdown files to process..."
+
+foreach ($file in $mdFiles) {
+    try {
+        # Read the file content
+        $content = Get-Content -Path $file.FullName -Raw -ErrorAction Stop
+
+        # Check if the file already has the noindex tag
+        if ($content -match '<meta\s+name="robots"\s+content="noindex"') {
+            Write-Host "Skipping (already has noindex): $($file.FullName)"
+            $skippedCount++
+            continue
+        }
+
+        # Add the meta tag at the beginning of the file
+        $newContent = $metaTag + "`r`n`r`n" + $content
+
+        # Write the updated content back to the file
+        Set-Content -Path $file.FullName -Value $newContent -NoNewline -ErrorAction Stop
+
+        Write-Host "Updated: $($file.FullName)"
+        $updatedCount++
+    }
+    catch {
+        Write-Host "ERROR processing $($file.FullName): $_" -ForegroundColor Red
+        $errorCount++
+    }
+}
+
+Write-Host "`n========== Summary =========="
+Write-Host "Total files: $($mdFiles.Count)"
+Write-Host "Updated: $updatedCount"
+Write-Host "Skipped (already had noindex): $skippedCount"
+Write-Host "Errors: $errorCount"
diff --git a/src/docs/_404.md b/src/docs/_404.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # 404 - Page not found
 
 

diff --git a/src/docs/_media/reusable-sample-media.md b/src/docs/_media/reusable-sample-media.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 ##  Reusable Snippet
 
 I am a markdown reusable snippet (on media)

diff --git a/src/docs/_sidebar.md b/src/docs/_sidebar.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 <!-- Table of Contents -->
 
 - [**Get Started with Spot**](connect-your-cloud-provider/)

diff --git a/src/docs/administration/README.md b/src/docs/administration/README.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Administration
 
 You can easily manage users, permissions, and accounts in Spot:

diff --git a/src/docs/administration/_sidebar.md b/src/docs/administration/_sidebar.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 <!-- Table of Contents -->
 
 - <a href="/" class="sidebar-home"><i data-feather="arrow-left" class="sidebar-back-icon"></i>Back to Home</a>

diff --git a/src/docs/administration/api/README.md b/src/docs/administration/api/README.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Spot API Administration
 
 The Spot API reference is available as an OpenAPI Specification.

diff --git a/src/docs/administration/api/aks-permissions-desc.md b/src/docs/administration/api/aks-permissions-desc.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 #   AKS Permissions
 
 This topic describes:

diff --git a/src/docs/administration/api/create-api-token.md b/src/docs/administration/api/create-api-token.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Create an API Token
 
 You can create permanent and temporary tokens:

diff --git a/src/docs/administration/api/spot-policy-aks-azure.md b/src/docs/administration/api/spot-policy-aks-azure.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Spot Policy in Azure (AKS)
 
 This is the latest Spot policy in Azure:

diff --git a/src/docs/administration/api/spot-policy-in-aws.md b/src/docs/administration/api/spot-policy-in-aws.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Spot Policy in AWS
 
 You can find and modify your Spot Policy in the [AWS IAM Console](https://console.aws.amazon.com/iam/home#/policies).

diff --git a/src/docs/administration/api/spot-policy-in-azure.md b/src/docs/administration/api/spot-policy-in-azure.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 <html>
 <script>
         fetch('https://spotinst-public.s3.amazonaws.com/assets/azure/custom_role_file.json')

diff --git a/src/docs/administration/api/spot-policy-in-gcp.md b/src/docs/administration/api/spot-policy-in-gcp.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Spot Policy in GCP
 
 You can find and modify your Spot Policy in the [GCP IAM Console](https://console.cloud.google.com/iamadmin/).

diff --git a/src/docs/administration/api/whitelist-ips.md b/src/docs/administration/api/whitelist-ips.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Permit List IP Addresses
 
 Spot permit list IP addresses are required for integrations to work as expected. The IP must be permit-listed on the Primary nodes of Rancher, HCS, Kubernetes, Nomad, and Docker Swarm.

diff --git a/src/docs/administration/groups/README.md b/src/docs/administration/groups/README.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Groups
 
 In Spot, a group is a set of [users](administration/users-a/) who have the same [policies](administration/policies/). You use groups to assign or modify policies for several users at once. You can use different types of groupings for managing users, for example:

diff --git a/src/docs/administration/groups/create-new-group.md b/src/docs/administration/groups/create-new-group.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Create New Group
 
 See [Groups](https://docs.spot.io/administration/groups/).
diff --git a/src/docs/administration/identity-providers/README.md b/src/docs/administration/identity-providers/README.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Identity Providers
 
 You can choose from several major identity providers to manage user authentication with Spot. Identity providers create connections between cloud computing resources and users. This minimizes signing in for users when they use mobile and roaming applications.

diff --git a/src/docs/administration/identity-providers/adfs-saml-authentication.md b/src/docs/administration/identity-providers/adfs-saml-authentication.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # AD FS SAML Authentication
 
 Active Directory Federation Services (AD FS or ADFS) is one of the leading identity provider (IDP) solutions in the market. You can configure your Spot account to be authenticated using the SAML protocol using AD FS.

diff --git a/src/docs/administration/identity-providers/azure-active-directory-integration.md b/src/docs/administration/identity-providers/azure-active-directory-integration.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Azure Active Directory Integration
 
 Manage Access with Azure Active Directory. For Spot users managing accounts in Azure Active Directory, Spot has an approved application in the Active Directory Gallery.

diff --git a/src/docs/administration/identity-providers/custom-saml-idp-configuration.md b/src/docs/administration/identity-providers/custom-saml-idp-configuration.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Custom SAML IDP Configuration
 
 Configuring an IDP to authenticate using SAML requires the:

diff --git a/src/docs/administration/identity-providers/define-organdrole-with-okta.md b/src/docs/administration/identity-providers/define-organdrole-with-okta.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Define OrgAndRole with Okta
 
 You can create multiple organization and role (OrgAndRole) definitions in Spot using Okta. Then you can use your Okta SSO to sign in to multiple organizations in Spot.

diff --git a/src/docs/administration/identity-providers/define-organdusergroups-with-okta.md b/src/docs/administration/identity-providers/define-organdusergroups-with-okta.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Define OrgAndUserGroups with Okta
 
 You can add a user to one or many user groups in an [organization](/administration/sso-access-control/organization-level-sso?id=organization-and-user-group) in Okta spotinst application:

diff --git a/src/docs/administration/identity-providers/google-saml-authentication.md b/src/docs/administration/identity-providers/google-saml-authentication.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Google SAML Authentication
 
 Manage Access with Google Workspace Directory. For Spot users managing accounts in Google Workspace Directory, Spot has an approved application in the App gallery.

diff --git a/src/docs/administration/identity-providers/okta-saml-authentication.md b/src/docs/administration/identity-providers/okta-saml-authentication.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Okta SAML Authentication
 
 SSO support makes it easy to manage your accounts and works with the most popular identity providers.

diff --git a/src/docs/administration/identity-providers/onelogin-saml-authentication.md b/src/docs/administration/identity-providers/onelogin-saml-authentication.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # OneLogin SAML Authentication
 
 This feature makes it easy to manage your accounts and works with the most popular identity providers.

diff --git a/src/docs/administration/identity-providers/scim.md b/src/docs/administration/identity-providers/scim.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # SCIM Integration
 
 Set up and use the system for cross-domain identity management (SCIM) integration for Spot in Okta. SCIM integration lets you automate user provisioning, updates, and deactivation.

diff --git a/src/docs/administration/notification-center/README.md b/src/docs/administration/notification-center/README.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Notification Center
 
 In the notification center, you can:

diff --git a/src/docs/administration/notification-center/event-policies/README.md b/src/docs/administration/notification-center/event-policies/README.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Event Policies
 
 The Spot console provides a robust and flexible tool for configuring and managing notifications. Spot uses a system of user-definable policies, providing granular management of event notifications and customization to fit different business cases. You can customize notification policies by:

diff --git a/...ocs/administration/notification-center/event-policies/create-security-policy.md b/...ocs/administration/notification-center/event-policies/create-security-policy.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Create a Security Policy
 
 You can create notifications for security resources.

diff --git a/src/docs/administration/notification-center/event-policies/create.md b/src/docs/administration/notification-center/event-policies/create.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Create a Compute Policy
 
 You can create notifications for compute products, such as Elastigroup and Ocean resources.

diff --git a/src/docs/administration/notification-center/notifications/README.md b/src/docs/administration/notification-center/notifications/README.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 <meta name=“robots” content=“noindex”>
 
 # Notifications

diff --git a/src/docs/administration/notification-center/notifications/read.md b/src/docs/administration/notification-center/notifications/read.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 <meta name=“robots” content=“noindex”>
 
 # Read Notifications

diff --git a/src/docs/administration/notification-center/z-create-a-notification-policy.md b/src/docs/administration/notification-center/z-create-a-notification-policy.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Create a Notification Policy
 
 This page describes the procedures to create a new notification policy in Spot console’s Notification Center.

diff --git a/src/docs/administration/notification-center/z-edit-a-notification-policy.md b/src/docs/administration/notification-center/z-edit-a-notification-policy.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Edit a Notification Policy
 
 Once you have created a notification policy, you can edit it to further customize the policy configuration and keep it up to date with the changing needs of your business.

diff --git a/src/docs/administration/organizations/README.md b/src/docs/administration/organizations/README.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Organizations and Accounts
 
 When you set up your Spot account, you create an organization and one or more account entities. You can set up multiple organizations if required. Within an organization, you can define multiple accounts for different teams or projects in the organization. Each account can be set up to use any supported cloud service provider and cloud service provider account.

diff --git a/src/docs/administration/organizations/billing-details.md b/src/docs/administration/organizations/billing-details.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Billing
 
 ## Set Up Payment Method

diff --git a/src/docs/administration/organizations/multitenancy.md b/src/docs/administration/organizations/multitenancy.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Multitenancy
 
 You can use multitenancy to create hierarchies in your Spot organizations. You can set up your child orgs to use role-based access control (RBAC). Admins for your parent orgs can have admin rights for the child orgs.

diff --git a/src/docs/administration/organizations/switch-organization.md b/src/docs/administration/organizations/switch-organization.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 <meta name=“robots” content=“noindex”>
 
 # Switch Organization

diff --git a/src/docs/administration/policies/README.md b/src/docs/administration/policies/README.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Permission Policies
 
 In Spot, a permission policy is a set of one or more permissions. When a policy is attached to a [user](administration/users-a/) or a [group](administration/groups/) of users, the policy grants its permissions to those users. A permission policy can apply to one or more individual Spot accounts, or a policy can apply to an entire Spot organization.

diff --git a/src/docs/administration/release-notes-core/README.md b/src/docs/administration/release-notes-core/README.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 #  Administration Release Notes
 
 * **ADM-0003 July 23, 2025**: The Spot console has updated [vCPU](administration/vcpu) and [Savings](administration/savings) pages, offering improved visibility and usability for resource and cost optimization.

diff --git a/src/docs/administration/savings.md b/src/docs/administration/savings.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Savings
 
 You can view how much you saved using spot instances instead of on-demand instances.

diff --git a/src/docs/administration/sso-access-control/README.md b/src/docs/administration/sso-access-control/README.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # SSO Access Control
 
 In the console, you can enable single sign-on (SSO) for your organization.

diff --git a/src/docs/administration/sso-access-control/account-level-sso.md b/src/docs/administration/sso-access-control/account-level-sso.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Account-Level SSO
 
 Assign account permissions with SAML attribute. For account-level login, you can grant a user permissions to accounts per [user role](administration/users/) and per [permission policy](administration/policies/). These are defined using SAML attributes. The attributes allow login to different accounts by the same user and the same IDP app while setting the roles dynamically on each request.

diff --git a/src/docs/administration/sso-access-control/organization-level-sso.md b/src/docs/administration/sso-access-control/organization-level-sso.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Organization-Level SSO
 
 For organization-level login, you can give a user permissions to an organization based on their role or user group using a SAML attribute. This lets a user sign in to different organizations using the same user and IDP app. The user can different permissions for each organization.

diff --git a/src/docs/administration/users-a/README.md b/src/docs/administration/users-a/README.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Users
 
 In Spot, a user is a person who accesses the Spot console to perform any action such as viewing information, producing reports, or creating and configuring spot clusters.

diff --git a/src/docs/administration/users-a/create-new-user.md b/src/docs/administration/users-a/create-new-user.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 <meta name=“robots” content=“noindex”>
 
 # Create New User

diff --git a/src/docs/administration/users-a/edit-user-details.md b/src/docs/administration/users-a/edit-user-details.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 <meta name=“robots” content=“noindex”>
 
 # Edit User Details

diff --git a/src/docs/administration/users/README.md b/src/docs/administration/users/README.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Users and Roles
 
 When you create a user, you must define a role in order to set the limitations of the specific user inside the account and organization.

diff --git a/src/docs/administration/users/add-users.md b/src/docs/administration/users/add-users.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Add Users
 
 ## Organization Tab

diff --git a/src/docs/administration/users/configure-email-notifications.md b/src/docs/administration/users/configure-email-notifications.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Configure Email Notifications
 
 By default, Spot will notify all the users in your account for every error or warning event (Unless they unsubscribe from the service). You can customize Elastigroup Notifications to send notifications for the events that matter to you.

diff --git a/src/docs/administration/users/configure-slack-notifications.md b/src/docs/administration/users/configure-slack-notifications.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Configure Slack Notification
 
 Elastigroup notifications can be sent automatically to a pre-defined Slack channel.

diff --git a/src/docs/administration/vcpu.md b/src/docs/administration/vcpu.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # vCPU
 
 The vCPU page gives you accurate, detailed visibility into vCPU consumption across your organization. It helps you track, optimize, and manage your compute resources more effectively. This improves your cost control and operational efficiency.

diff --git a/src/docs/connect-your-cloud-provider/README.md b/src/docs/connect-your-cloud-provider/README.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 ## Products
 
 * [Ocean](ocean/)

diff --git a/src/docs/connect-your-cloud-provider/additional-account.md b/src/docs/connect-your-cloud-provider/additional-account.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Connect an Additional Account
 
 Once you have completed your Spot registration and connected your first account (either a linked or a managed account), you can connect additional accounts to your Organization in Spot. Your additional accounts can be from the same cloud provider or from different ones (AWS, GCP, or Azure).

diff --git a/src/docs/connect-your-cloud-provider/aws-account.md b/src/docs/connect-your-cloud-provider/aws-account.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Connect your AWS Account to Spot
 
 In this procedure, you will connect your cloud provider account to Spot in order to provide the Spot platform with a set of permissions to manage instances on your behalf.

diff --git a/src/docs/connect-your-cloud-provider/azure-account.md b/src/docs/connect-your-cloud-provider/azure-account.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Connect your Azure Subscription to Spot
 
 This procedure covers authenticating your Spot account with Azure, which gives Spot the necessary permissions to launch and manage Azure resources on your behalf.

diff --git a/src/docs/connect-your-cloud-provider/azure-ea-account.md b/src/docs/connect-your-cloud-provider/azure-ea-account.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Connect Your Azure Billing Account to Spot
 
 This procedure describes how to set up Spot account access to Azure EA read only data, which gives Spot the necessary permissions to pull Azure data and process it for the [Eco Azure Dashboard](eco/azure-tutorials/view-your-savings).

diff --git a/src/docs/connect-your-cloud-provider/cost-analysis/README.md b/src/docs/connect-your-cloud-provider/cost-analysis/README.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Analyze your Costs
 
 The Cost Analysis page provides insights on past, current, and future cloud costs.

diff --git a/src/docs/connect-your-cloud-provider/cost-analysis/save-reports.md b/src/docs/connect-your-cloud-provider/cost-analysis/save-reports.md
@@ -1,3 +1,5 @@
+<meta name="robots" content="noindex">
+
 # Save Analysis Reports
 
 The Cloud Analyzer [Cost Analysis](connect-your-cloud-provider/cost-analysis/) page provides a detailed breakdown of your organization's cloud compute costs. When you create customized Spend Analysis reports using the filters and grouping options, you can save each report for quick reference and future follow up on spending. By saving your customized reports, you can re-use the same filters and grouping options without having to reset them each time you need a report. This saves time for you and helps you to obtain exactly the same report parameters and presentation whenever you review reports.
Original file line number	Diff line number	Diff line change
		@@ -1,3 +1,5 @@
		<meta name="robots" content="noindex">

		# 404 - Page not found


Expand Down