{"id":137,"date":"2026-05-17T04:49:42","date_gmt":"2026-05-17T04:49:42","guid":{"rendered":"https:\/\/siteinfocheck.com\/blog\/?p=137"},"modified":"2026-05-17T04:51:45","modified_gmt":"2026-05-17T04:51:45","slug":"why-your-website-shows-not-secure","status":"publish","type":"post","link":"https:\/\/siteinfocheck.com\/blog\/why-your-website-shows-not-secure\/","title":{"rendered":"Why Your Website Shows \u201cNot Secure\u201d (Even With HTTPS)"},"content":{"rendered":"<h3><span class=\"ez-toc-section\" id=\"HTTPS_%E2%80%93_The_standard_for_most_people_to_check_security_against\"><\/span><strong>HTTPS \u2013 The standard for most people to check security against<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>About twenty years ago, HTTPS was just a brand new technology that was only expected to be active on sensitive endpoints and for important actions, like banking or logins. But today, people expect to see it everywhere, even non-technical people know that if it is not HTTPS, then it is not safe. Ok, that is mostly true, but how come when even the website has HTTPS, we still get a Not secure warning on our browser? What is happening in the background? We will talk about it in this article.<\/p><div id=\"ez-toc-container\" class=\"ez-toc-v2_0_83 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/siteinfocheck.com\/blog\/why-your-website-shows-not-secure\/#HTTPS_%E2%80%93_The_standard_for_most_people_to_check_security_against\" >HTTPS \u2013 The standard for most people to check security against<\/a><\/li><\/ul><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-1'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/siteinfocheck.com\/blog\/why-your-website-shows-not-secure\/#Why_Your_Website_Shows_%E2%80%9CNot_Secure%E2%80%9D_Even_With_HTTPS\" >Why Your Website Shows \u201cNot Secure\u201d (Even With HTTPS)<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/siteinfocheck.com\/blog\/why-your-website-shows-not-secure\/#Expired_or_Invalid_SSL_Certificate\" >Expired or Invalid SSL Certificate<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/siteinfocheck.com\/blog\/why-your-website-shows-not-secure\/#HTTPS_Not_Enforced_Site-Wide\" >HTTPS Not Enforced Site-Wide<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/siteinfocheck.com\/blog\/why-your-website-shows-not-secure\/#Browser_Cache_or_Old_Redirects\" >Browser Cache or Old Redirects<\/a><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/siteinfocheck.com\/blog\/why-your-website-shows-not-secure\/#How_Browsers_Decide_to_Show_%E2%80%9CNot_Secure%E2%80%9D\" >How Browsers Decide to Show \u201cNot Secure\u201d<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/siteinfocheck.com\/blog\/why-your-website-shows-not-secure\/#How_to_Diagnose_the_Problem_Correctly\" >How to Diagnose the Problem Correctly<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/siteinfocheck.com\/blog\/why-your-website-shows-not-secure\/#What_to_Look_For_in_the_Results\" >What to Look For in the Results<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/siteinfocheck.com\/blog\/why-your-website-shows-not-secure\/#What_Usually_Fixes_the_Issue\" >What Usually Fixes the Issue<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/siteinfocheck.com\/blog\/why-your-website-shows-not-secure\/#FAQs_%E2%80%9CNot_Secure%E2%80%9D_Browser_Warnings\" >FAQs: \u201cNot Secure\u201d Browser Warnings<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/siteinfocheck.com\/blog\/why-your-website-shows-not-secure\/#Is_my_website_unsafe_if_it_shows_%E2%80%9CNot_Secure%E2%80%9D\" >Is my website unsafe if it shows \u201cNot Secure\u201d?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/siteinfocheck.com\/blog\/why-your-website-shows-not-secure\/#Will_%E2%80%9CNot_Secure%E2%80%9D_hurt_my_SEO\" >Will \u201cNot Secure\u201d hurt my SEO?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/siteinfocheck.com\/blog\/why-your-website-shows-not-secure\/#Does_HTTPS_automatically_renew_SSL_certificates\" >Does HTTPS automatically renew SSL certificates?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/siteinfocheck.com\/blog\/why-your-website-shows-not-secure\/#Can_ads_or_third-party_scripts_cause_this_warning\" >Can ads or third-party scripts cause this warning?<\/a><\/li><\/ul><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n\n<p>Before we begin, I must say that warnings are not always because the website itself or you. Maybe your <strong>Internet Service Provider (ISP) or any regulations you might have in your region,<\/strong> does something <strong>sneaky<\/strong> that you are not aware of. That\u2019s not common, but you might not want to overlook that if you live in some specific parts of the beautiful planet earth.<\/p>\n<p><strong>A small warning:<\/strong><\/p>\n<p>Just so you know, one other very important thing that triggers the not secure warning, is that when someone is listening to your connection! For example, if someone in your home is connected to the same router as you and performs a <strong>Man In The Middle attack (MITM) attack<\/strong> with a method like <strong>ARP Spoofing<\/strong>, you will likely see the warning on all websites you visit. So be cautious specially in places that tell you <strong>\u201cWe have free Wi-Fi, be our guest\u201d<\/strong>.<\/p>\n<p>In this blog, we will be discussing issues related to HTTPS configuration and browser\u2019s behavior.<\/p>\n<h1><span class=\"ez-toc-section\" id=\"Why_Your_Website_Shows_%E2%80%9CNot_Secure%E2%80%9D_Even_With_HTTPS\"><\/span><strong>Why Your Website Shows \u201cNot Secure\u201d (Even With HTTPS)<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h1>\n<p>If the website uses HTTPS but still shows a <strong>\u201cNot Secure\u201d<\/strong> warning in the browser, you\u2019re not alone. It happens more often than you might think, somehow we can say that <strong>\u201cNot Secure\u201d<\/strong> does not always mean that it\u2019s not secure.<br \/>\nThis is a common issue for website owners and small businesses and in most cases, it does <strong>not<\/strong> mean your entire site is unsafe. It usually means there is a <strong>specific configuration or content problem<\/strong> that needs fixing.<\/p>\n<p>we\u2019ll explain why this happens, clear up some common misunderstandings about HTTPS, and show you how to diagnose the issue correctly.<\/p>\n<p><strong>The Biggest Myths About HTTPS<\/strong><\/p>\n<p>Many users or website owners assume:<\/p>\n<p>\u201cIf a site has HTTPS, it should always be secure.\u201d<\/p>\n<p>That\u2019s not entirely true.<\/p>\n<p>HTTPS simply means that a website <strong>can<\/strong> use encrypted connections. HTTPS is supposed to protect your communication with the website, so no one can see what you tell the website and what it tells you back. In general HTTPS aims to protect the integrity of your communication and make sure that messages get to their destination safe.<br \/>\nBy just having HTTPS in beginning of an address, it does not mean that:<\/p>\n<ul>\n<li>The SSL certificate is valid<\/li>\n<li>All site content is loaded securely, some maybe, some not<\/li>\n<li>The certificate is correctly installed: The certificate validity and proper configuration are two different things.<\/li>\n<li>Browsers fully trust the configuration<\/li>\n<\/ul>\n<p>Because of this, browsers like Chrome, Edge, and Safari may still show <strong>\u201cNot Secure\u201d<\/strong> even when HTTPS is enabled.<\/p>\n<p><strong>Most Common Reasons a Site Shows \u201cNot Secure\u201d Even With HTTPS<\/strong><\/p>\n<ol>\n<li><strong> Mixed Content (Most Common Cause)<\/strong><\/li>\n<\/ol>\n<p>This happens when:<\/p>\n<ul>\n<li>The main page loads over HTTPS<\/li>\n<li>But some resources (images, scripts, CSS) still load over HTTP<\/li>\n<\/ul>\n<p>Browsers treat this as a security risk because unsecured elements can be tampered with.<\/p>\n<p>This problem often arises when there are multiple sources of information or content to be loaded into the website. This gets worse when the infrastructure of a website or a company gets bigger. Imagine you have multiple websites on multiple servers, too many code files, images, fonts, videos, external sources of data that you need their service and etc. The developer should always pay attention to the architecture so all resources would be loaded under a <strong>secure connection channel<\/strong> like HTTPS.<\/p>\n<p><strong>Example:<\/strong><br \/>\nA WordPress site migrated to HTTPS, but old image URLs in blog posts still use http:\/\/.<\/p>\n<ol start=\"2\">\n<li>\n<h3><span class=\"ez-toc-section\" id=\"Expired_or_Invalid_SSL_Certificate\"><\/span><strong> Expired or Invalid SSL Certificate<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<\/li>\n<\/ol>\n<p>SSL certificates have expiration dates and also need to be renewed once in a while.<br \/>\nIf the certificate expires, even by one day, browsers will show warnings immediately.<\/p>\n<p>Other certificate issues include:<\/p>\n<ul>\n<li>Certificate issued for a different domain but used for another<\/li>\n<li>Missing intermediate certificates<\/li>\n<li>Incorrect installation on the server<\/li>\n<\/ul>\n<ol start=\"3\">\n<li>\n<h3><span class=\"ez-toc-section\" id=\"HTTPS_Not_Enforced_Site-Wide\"><\/span><strong> HTTPS Not Enforced Site-Wide<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<\/li>\n<\/ol>\n<p>If:<\/p>\n<ul>\n<li>Your homepage loads with HTTPS<\/li>\n<li>But internal pages or redirects fall back to HTTP<\/li>\n<\/ul>\n<p>Browsers may warn users depending on how they land on the site.<\/p>\n<p>This is common when:<\/p>\n<ul>\n<li>HTTP \u2192 HTTPS redirects are misconfigured: Your website is supposed to tell users who visit the HTTP address to move to the HTTPS version, but sometimes there might be a misconfiguration on the server or the website code base, that prevents the browser from doing that automatically.<\/li>\n<li>CDN or hosting settings are inconsistent<\/li>\n<\/ul>\n<ol start=\"4\">\n<li>\n<h3><span class=\"ez-toc-section\" id=\"Browser_Cache_or_Old_Redirects\"><\/span><strong> Browser Cache or Old Redirects<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<\/li>\n<\/ol>\n<p>Sometimes the issue isn\u2019t the certificate at all.<\/p>\n<p>Browsers aggressively cache:<\/p>\n<ul>\n<li>Old redirects<\/li>\n<li>Security policies<\/li>\n<li>Previous certificate data<\/li>\n<\/ul>\n<p>This can cause warnings to persist even after fixing the real issue. In other words, the issue has been fixed on the website, but browser shows you the previous version, the last thing you saw. Browser does that for the sake of load speed but sometimes causes minor problems like that. So always make sure you viewing the latest version of the website. One thing you can do is to know that whether this is the source of the problem, you can hard reload. In most modern browsers there are key shortcuts for that. For most of them, you can hold <strong>control and shift buttons<\/strong>, the press <strong>R<\/strong>. This way everything will be requested again from the server so you will see the latest version.<\/p>\n<h4><span class=\"ez-toc-section\" id=\"How_Browsers_Decide_to_Show_%E2%80%9CNot_Secure%E2%80%9D\"><\/span><strong>How Browsers Decide to Show \u201cNot Secure\u201d<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n<p>Modern browsers look at <strong>multiple signals<\/strong>, not just HTTPS:<\/p>\n<ul>\n<li>Certificate validity<\/li>\n<li>Encryption strength<\/li>\n<li>Mixed content<\/li>\n<li>User actions (like form inputs)<\/li>\n<li>Known unsafe configurations<\/li>\n<\/ul>\n<p>That\u2019s why two browsers may show <strong>different warnings<\/strong> for the same site. HTTPS is not a true or false kind of situation, there are multiple factors that needs to be checked by browsers.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"How_to_Diagnose_the_Problem_Correctly\"><\/span><strong>How to Diagnose the Problem Correctly<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Instead of guessing, it\u2019s best to <strong>check your SSL configuration directly<\/strong>.<\/p>\n<p>An online <a href=\"https:\/\/siteinfocheck.com\/ssl-checker\">SSL checker<\/a> can help you:<\/p>\n<ul>\n<li>Verify if the certificate is valid<\/li>\n<li>See expiration dates<\/li>\n<li>Detect missing certificate chains<\/li>\n<li>Identify common configuration issues<\/li>\n<\/ul>\n<p>It will give you a clearer version of the certificate that the browsers see and decides if a website is secure or not.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-143 size-large\" src=\"https:\/\/siteinfocheck.com\/blog\/wp-content\/uploads\/2026\/05\/ssl-checker-site-info-1024x695.png\" alt=\"ssl checker site info\" width=\"1024\" height=\"695\" srcset=\"https:\/\/siteinfocheck.com\/blog\/wp-content\/uploads\/2026\/05\/ssl-checker-site-info-1024x695.png 1024w, https:\/\/siteinfocheck.com\/blog\/wp-content\/uploads\/2026\/05\/ssl-checker-site-info-300x204.png 300w, https:\/\/siteinfocheck.com\/blog\/wp-content\/uploads\/2026\/05\/ssl-checker-site-info-768x521.png 768w, https:\/\/siteinfocheck.com\/blog\/wp-content\/uploads\/2026\/05\/ssl-checker-site-info.png 1263w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/p>\n<h3><span class=\"ez-toc-section\" id=\"What_to_Look_For_in_the_Results\"><\/span><strong>What to Look For in the Results<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li>Certificate status: valid or invalid<\/li>\n<li>Expiration date<\/li>\n<li>Domain match<\/li>\n<li>Warnings about mixed or incomplete chains<\/li>\n<\/ul>\n<p>This gives you a clear starting point before making changes on your server or hosting panel.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"What_Usually_Fixes_the_Issue\"><\/span><strong>What Usually Fixes the Issue<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Depending on the cause, fixes may include:<\/p>\n<ul>\n<li>Replacing HTTP links with HTTPS<\/li>\n<li>Renewing or reinstalling the SSL certificate<\/li>\n<li>Enforcing HTTPS redirects site-wide<\/li>\n<li>Clearing browser cache and testing in incognito mode<\/li>\n<li>Updating CDN or hosting SSL settings<\/li>\n<\/ul>\n<p>The key is identifying <strong>which problem you actually have<\/strong> before applying fixes. If this is not done and we just test random methods, this might turn a very simple issue into a complex one to resolve.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"FAQs_%E2%80%9CNot_Secure%E2%80%9D_Browser_Warnings\"><\/span><strong>FAQs: \u201cNot Secure\u201d Browser Warnings<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<div class=\"faq-item\">\n<h3><span class=\"ez-toc-section\" id=\"Is_my_website_unsafe_if_it_shows_%E2%80%9CNot_Secure%E2%80%9D\"><\/span>Is my website unsafe if it shows \u201cNot Secure\u201d?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Not necessarily. In many cases, the warning is triggered by an SSL, HTTPS, or mixed content configuration issue rather than an actual security breach.<\/p>\n<\/div>\n<div class=\"faq-item\">\n<h3><span class=\"ez-toc-section\" id=\"Will_%E2%80%9CNot_Secure%E2%80%9D_hurt_my_SEO\"><\/span>Will \u201cNot Secure\u201d hurt my SEO?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Indirectly, yes. Security warnings can reduce user trust, increase bounce rates, and lower conversions \u2014 all of which may negatively affect SEO performance.<\/p>\n<\/div>\n<div class=\"faq-item\">\n<h3><span class=\"ez-toc-section\" id=\"Does_HTTPS_automatically_renew_SSL_certificates\"><\/span>Does HTTPS automatically renew SSL certificates?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Only if your hosting provider or certificate authority supports automatic SSL renewal. Otherwise, certificates must be renewed manually before expiration.<\/p>\n<\/div>\n<div class=\"faq-item\">\n<h3><span class=\"ez-toc-section\" id=\"Can_ads_or_third-party_scripts_cause_this_warning\"><\/span>Can ads or third-party scripts cause this warning?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Yes. External scripts, ads, or embedded resources loaded over HTTP instead of HTTPS can trigger mixed content and \u201cNot Secure\u201d browser warnings.<\/p>\n<\/div>\n<p><strong>Final Thoughts<\/strong><\/p>\n<p>Seeing \u201cNot Secure\u201d on an HTTPS website is frustrating, but it\u2019s usually <strong>fixable<\/strong> once you understand the cause.<br \/>\nInstead of assuming the worst, focus on <strong>diagnosing the exact issue<\/strong>, checking your SSL setup, and fixing configuration gaps.<\/p>\n<p>A properly configured HTTPS site builds trust, protects users, and avoids unnecessary browser warnings, especially important for businesses targeting users in the US and Australia.<\/p>\n<p>Stay safe friend<\/p>\n","protected":false},"excerpt":{"rendered":"<p>HTTPS \u2013 The standard for most people to check security against About twenty years ago, HTTPS was just a brand new technology that was only expected to be active on sensitive endpoints and for important actions, like banking or logins. But today, people expect to see it everywhere, even non-technical people know that if it [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":141,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-137","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/siteinfocheck.com\/blog\/wp-json\/wp\/v2\/posts\/137","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/siteinfocheck.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/siteinfocheck.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/siteinfocheck.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/siteinfocheck.com\/blog\/wp-json\/wp\/v2\/comments?post=137"}],"version-history":[{"count":2,"href":"https:\/\/siteinfocheck.com\/blog\/wp-json\/wp\/v2\/posts\/137\/revisions"}],"predecessor-version":[{"id":144,"href":"https:\/\/siteinfocheck.com\/blog\/wp-json\/wp\/v2\/posts\/137\/revisions\/144"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/siteinfocheck.com\/blog\/wp-json\/wp\/v2\/media\/141"}],"wp:attachment":[{"href":"https:\/\/siteinfocheck.com\/blog\/wp-json\/wp\/v2\/media?parent=137"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/siteinfocheck.com\/blog\/wp-json\/wp\/v2\/categories?post=137"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/siteinfocheck.com\/blog\/wp-json\/wp\/v2\/tags?post=137"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}