--- schema_version: "1" id: a1e7402edf4d3da64009cfc73e72ca9ad71f4c71de6c7579d3a2581d5077a454 title: Use the URL Request Analyzer collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_using_the_url_request_analyzer.md canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_using_the_url_request_analyzer.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 5dd2f9194bfb0979f1465c0405e516c4dc82523421d0babce494c3fd0f633dbb description: The URL Request Analyzer provides you with detailed information on specific URL requests. This tool can help you understand how B2C Commerce processes Storefront URL requests and which configuration it uses to open the corresponding storefront page. It can help identify the root cause of invalid URLs, 404 error pages, and URLs not resulting in the expected target. products: - Commerce - B2C Commerce release: "264" --- # Use the URL Request Analyzer The URL Request Analyzer provides you with detailed information on specific URL requests. This tool can help you understand how B2C Commerce processes Storefront URL requests and which configuration it uses to open the corresponding storefront page. It can help identify the root cause of invalid URLs, 404 error pages, and URLs not resulting in the expected target. You can also use this tool to test sensitive configurations with potential impact on SEO, enabling you to identify possible issues before go-live. If you have enabled password protection for your storefront, some redirects (for example, to secure protocol) or events (for example, entering the password) occur before you get access. If you’re testing URLs, these events appear as high-level information. Results are provided and visualized for the following requests: - Site and locale identification such as site mappings from path or aliases file and locale mappings - Path mappings for products and content, (archived) categories/folders/pipelines with or without search refinements, and sitemaps - Pipeline and controller requests - Service destinations (shop/data API) - Redirects such as hostname, static and dynamic redirects, URL redirect mappings, search driven redirects, URL search refinement values, and automatic redirects for outdated mappings (that is, SEO-friendly Search Refinement URLs) - Custom code (if the redirect was initiated within a custom pipeline/controller) 1. Click App Launcher ![App Launcher](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/cc/b2c_merchandiser_administrator/images/appLauncher.png), and then select **Merchant Tools** | **Site** | **SEO & Discoverability** | **URL Request Analyzer**. 2. Enter the URL you want to analyze into the URL field. - Absolute URL with protocol (for example, `https://www.my-host.com/mens/`) or without protocol (HTTP protocol is used, for example, `www.my-host.com/mens/`). - Relative URL starting with slash (HTTP protocol and current request hostname is used, for example, `/us/mens/?param=aValue`). 3. Filter results as follows: - None (all) - Hosts only: To see host resolving information (and other basic resolve information) - Redirects only: To see redirect resolving information (and other basic resolve information) 4. Click **Add**. An entry is created for the URL with a preview link. The preview link has a recording ID, which is mandatory for recording information. Information is only recorded for links in this user interface. There can be up to a maximum of five links per site. Entries can be removed with the x button. Each site has an independent list. 5. Click the Preview icon ![Preview magnifying glass icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/cc/b2c_merchandiser_administrator/images/b2c_preview_icon_1.gif) for an entry to process a request to the storefront. If the storefront page renders successfully: 1. Close the browser tab showing the storefront. 2. Return to Business Manager URL Request Analyzer page. 3. Click **Refresh** or change the filter and then click **Refresh**. 6. Click an added URL object to open it to review the recorded information. 1. Click the ![plus sign](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/cc/b2c_merchandiser_administrator/images/b2c_expand_icon.gif) icon to open more details. 2. Click the ![minus sign](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/cc/b2c_merchandiser_administrator/images/b2c_contract_icon.gif) icon to contract the view. 3. Click the ![expanding arrows](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/cc/b2c_merchandiser_administrator/images/b2c_table_icon.gif) icon to expand the information completely and in table format. The following are the resolve types (explained via this URL example: `http://system-a.system-b.dw.demandware.net/s/SiteGenesis/womens/clothing/?lang=en_US`): - Site mapping: How the request URL identifies the site, for example, the request site `SiteGenesis` resolves from path `/s/SiteGenesis`. - Locale mapping: The request's available locale in the Pipeline Dictionary, for example, the locale `en_US` as identified from parameters. - Pipeline mapping: The pipeline requested to be called, as resolved from the request path, for example, the category URL, `womens/clothing` was mapped and forwarded to `/Sites-SiteGenesis-Site/en_US/Search-Show?cgid=womens-clothing`. - Process Pipeline/Controller: The pipeline/controller that is called for this request, for example, `OnRequest-Do, OnSession-Do, Search-Show`. - Redirect mapping: Used if one or more redirects occur for this request. The `RedirectURL-Start` pipeline identifies redirects, or they occur before any pipeline execution. - Color groups: Optional colors in the Resolve Information section, which can occur if a mapping type occurs multiple times in the same way. The same color marks the same mappings. If there is more than one of a resolve type in the results, Choose to show the first iteration, or all results. For example, if the results show two Process Pipelines lines of `OnRequest-Do` and `Product-ShowInCategory`, you can choose to show the first line or both lines. 7. If you changed the related configuration and want to review B2C Commerce behavior, repeat steps 5 and 6 and review the updated information.