Schema Manager Onboading Requirements

Overview

To ensure a seamless onboarding experience for Schema Manager, agencies should gather key access credentials and implementation details in advance. This checklist will help you deploy structured data efficiently across your client's website and begin collecting performance insights right away.

 

Background

Schema Manager allows agencies to deploy and manage structured data (schema markup) at scale across client websites. Proper onboarding ensures accurate deployment, faster time to value, and measurable results through improved search visibility.

 

Who is this for?

This guide is for agencies onboarding new clients to a schema markup solution. It ensures all necessary tools, access, and technical configurations are prepared before the schema solution is activated.

 

Step-by-Step Instructions

1. Grant Admin Access to Key Tools

Agencies must request access to the following platforms from their clients:

Google Search Console (GSC)

Access Required: Full/Admin access

Purpose: Allows schema performance monitoring, indexing validation, and diagnostics

Who to Add: Use your designated agency schema email (e.g., exampleagency@gmail.com)

Google Search Console Access Instructions

Google Analytics (for enterprise clients)

Access Required: Full/Admin access

Purpose: Enables mapping schema impact to user behavior and conversions

Who to Add: Same designated email as above

 

2. Implement Schema Script

The Schema Manager requires a JavaScript loader to be present across relevant web pages.

Options to Deploy the Schema Script:

Option 1:
Add the following script manually in the <head> section of the website: 

<script type="text/javascript" src="https://schema.milestoneinternet.com/schema/js/msschemaloader_faq.js"></script> <script type="text/javascript">msSchemaLoader();</script>

Option 2:
Deploy the script using a Tag Manager (e.g., Google Tag Manager, Adobe Tag Manager, or Tealium):

Required: Admin access to the client’s tag management tool

Who to Add: Your agency tag management email (e.g., exampleagency@gmail.com)

 

3. Whitelist Crawler IPs

Structured data implementation includes regular crawling for updates. Ensure the agency’s crawler IPs are whitelisted at the hosting or firewall level.

Share the following IPs with your client’s IT or web hosting team:

Production: 40.122.159.0

UAT: 20.120.37.221

Stage: 20.25.48.146

These IPs should be granted access similar to a developer or SEO team’s access level.

 

4. Select Target URLs for Schema Deployment

Work with your client to identify priority pages for schema markup. Aim to start with ~200 indexable pages.

Recommended Pages:

  • Homepage
  • Location Pages
  • Service or Product Pages
  • Blog Posts with rich content
  • Recipe Pages or FAQs
  • Category or Solution Pages
  • High-impression or revenue-driving pages

📌 If you're unsure, collaborate with your internal data or SEO team to select pages based on performance data (GSC, GA, etc.).

 

Glossary

  • Structured Data / Schema Markup: Code that helps search engines understand website content.
  • Google Search Console (GSC): A tool to monitor and optimize website performance in search.
  • Google Tag Manager: A tool to deploy and manage marketing or technical tags without editing site code.
  • Whitelist: A security setting that allows only approved IPs or domains to access a server or platform.
  •  

Tips for Agencies

  • Request access and technical implementation approvals as early as possible in your onboarding process.
  • Use a shared implementation tracker to stay aligned with client teams (IT, marketing, dev).
  • Confirm deployment via live page checks and structured data testing tools once the script is added.
  • Revisit and expand schema coverage as the website evolves or new content is added.

Was this article helpful?

Table of Contents

Related Articles