> For the complete documentation index, see [llms.txt](https://academy.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.pakk.io/ecommerce-launch-mega-checklist/seo-webmaster-analytics.md).
# SEO/Webmaster/Analytics
[More information on how Pakk helps with SEO](https://pakk.io/post/seo-guide)
[Guide to Google Services for E-Commerce Businesses](https://pakk.io/post/setting-up-google-services-ecommerce)
* Look up best practices for meta data and create good, concise and human readable: URLs, meta title and meta description. *Pakk sites - set all these SEO fields under the 'Web' tab for publishable entities like products, pages, posts etc*
* Make sure your pages are generating Twitter Card, Open Graph (Facebook) and Structured Data (Google) and embedding it correctly in the `` of your site. *Pakk sites - this is taken care of for you, just get the SEO fields filled out correctly.*
* Favicons and site manifests for all different browsers and devices. *Pakk sites - just set your 'favicon' logo in site setup, everything else is done for you.*
* Submit your site to Google Webmaster console and keep an eye out for errors, crawl problems and notifications. Try to use the "domain" verification method if possible for ease of maintenance.
* In the Webmaster Console, set up and submit your site's *sitemap*. If you platform allows for autogeneration, set up an upload schedule for the sitemap. *Pakk sites - you can always get the sitemap at `/sitemap.xml`. Set up a schedule for the sitemap to be downloaded daily.*
* Set up Google analytics and integrate the JS snippet into your site. *Pakk sites - just enter your Google analytics ID in site setup.*
* Use the Google 'Rich Snippets' testing tool to preview how Google sees your site and how it might generate snippets. Try to ensure that they are as rich as possible for all page types (product/post/page etc.). \*Pakk sites - you don't need to do this - we do it for you.
* Are you on Google business? Make sure you have claimed your business and keep the details up to date.
* Sign up for and active Google Merchant Center. Set up all your business details and if you are intended to run multiple sites/stores from the same account, ask for your account to be upgrade to a "Multi Brand" account.
* Get your product feed into Google Merchant Center. There are a variety of options for doing this, ranging from manual entry to CSV import to API integrations. \*Pakk customers - just choose the "Web Crawl" option and Google will automatically build a feed from the rich metadata we embed on each product page.
* Put the feed in Google Merchant Center to work by activating free listings and potentially linking with your adWords account and activating paid listings.
* Can people find your brand presence on social media? Include links to your profiles wherever possible. *Pakk sites - just set up your profiles in site setup and links will be shown throughout the site automatically.*
* Are you creating engaging and informative content on a regular basis? Is it easily discoverable within the site? Are posts cross-linked to product where relevant? *Pakk sites - use the 'Posts' and/or 'Feed' functionality to create content on a regular basis, link to the 'content homepage' from the main site homepage. Cross link products and posts with 'content tags'.*
\
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://academy.pakk.io/ecommerce-launch-mega-checklist/seo-webmaster-analytics.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.