<br />
<b>Notice</b>:  Function amp_has_paired_endpoint was called <strong>incorrectly</strong>. Function cannot be called before services are registered. The service ID &quot;paired_routing&quot; is not recognized and cannot be retrieved. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 2.1.1.) in <b>/home/atozsportsinfra/analystedge.in/wp-includes/functions.php</b> on line <b>5865</b><br />
<br />
<b>Notice</b>:  Function amp_is_available was called <strong>incorrectly</strong>. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 2.0.0.) in <b>/home/atozsportsinfra/analystedge.in/wp-includes/functions.php</b> on line <b>5865</b><br />
<br />
<b>Notice</b>:  Function amp_has_paired_endpoint was called <strong>incorrectly</strong>. Function cannot be called before services are registered. The service ID &quot;paired_routing&quot; is not recognized and cannot be retrieved. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 2.1.1.) in <b>/home/atozsportsinfra/analystedge.in/wp-includes/functions.php</b> on line <b>5865</b><br />
<br />
<b>Notice</b>:  Function amp_is_available was called <strong>incorrectly</strong>. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 2.0.0.) in <b>/home/atozsportsinfra/analystedge.in/wp-includes/functions.php</b> on line <b>5865</b><br />
<br />
<b>Notice</b>:  Function amp_is_available was called <strong>incorrectly</strong>. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 2.0.0.) in <b>/home/atozsportsinfra/analystedge.in/wp-includes/functions.php</b> on line <b>5865</b><br />
<br />
<b>Notice</b>:  Function amp_is_available was called <strong>incorrectly</strong>. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see <a href="https://wordpress.org/documentation/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 2.0.0.) in <b>/home/atozsportsinfra/analystedge.in/wp-includes/functions.php</b> on line <b>5865</b><br />
<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="//analystedge.in/main-sitemap.xsl"?>
<urlset xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:image="http://www.google.com/schemas/sitemap-image/1.1" xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd http://www.google.com/schemas/sitemap-image/1.1 http://www.google.com/schemas/sitemap-image/1.1/sitemap-image.xsd" xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
	<url>
		<loc>https://analystedge.in/?elementskit_template=header</loc>
		<lastmod>2024-12-30T04:00:06+00:00</lastmod>
		<image:image>
			<image:loc>https://analystedge.in/wp-content/uploads/2021/06/cropped-WhatsApp_Image_2021-06-29_at_10.39.17-removebg-preview-300x112.png</image:loc>
		</image:image>
	</url>
</urlset>
<!-- XML Sitemap generated by Rank Math SEO Plugin (c) Rank Math - rankmath.com -->
<!-- Served from cache in 0.001 second(s) (Memory usage: 1.47 KB) -->