{"id":49040,"date":"2019-11-18T23:32:45","date_gmt":"2019-11-18T15:32:45","guid":{"rendered":"https:\/\/www.hongkiat.com\/blog\/?p=49040"},"modified":"2022-10-18T20:12:08","modified_gmt":"2022-10-18T12:12:08","slug":"force-http-https-wordpress-apache-server","status":"publish","type":"post","link":"https:\/\/www.hongkiat.com\/blog\/force-http-https-wordpress-apache-server\/","title":{"rendered":"Forcing HTTP to HTTPS in WordPress (Apache Server)"},"content":{"rendered":"

You should always load your site with HTTPS. Aside from protecting your data integrity between your websites and your site users, HTTPS is now a requirement for many new browser APIs such as the Geolocation API<\/a>.<\/p>\n

HTTPS also carries on some weight in Google SERP ranking signal<\/a>. So ensuring that your site will always load from HTTPS is crucial. We\u2019ll show you how to do it with Apache in this tutorial.<\/p>\n

Note that before proceeding this step, make sure that you\u2019ve got the SSL cert installed and loaded in the server. Otherwise, check out our tutorial on Beginner\u2019s Guide to Website SSL Certs<\/a>.<\/p>\n

If it is all set, you can proceed to the next step.<\/p>\n

HTTP to HTTPS<\/h2>\n

If your WordPress website can be accessed directly at http:\/\/www.domain.com<\/code> and you want to direct all visitors from HTTP to HTTPS, then try either of the following .htaccess codes.<\/p>\n

Option 1: <\/h3>\n
\r\nRewriteEngine On\r\nRewriteCond %{HTTPS} !on\r\nRewriteRule (.*) https:\/\/%{HTTP_HOST}%{REQUEST_URI} [R=301,L]\r\n<\/pre>\n
Option 2:<\/h3>\n
\r\nRewriteEngine On\r\nRewriteCond %{SERVER_PORT} ^80$\r\nRewriteRule ^.*$ https:\/\/%{SERVER_NAME}%{REQUEST_URI} [R=301,L]\r\n<\/pre>\n
Explanation<\/h3>\n
Both option 1 and 2<\/strong> will redirect anyone accessing http:\/\/www.domain.com<\/code> to https:\/\/www.domain.com<\/code><\/p>\n
Option 1<\/strong> codes will check if the connection whether it\u2019s TLS\/SSL, while Option 2<\/strong> codes will check if the site runs on port 80<\/code> which, by default, is the port number of HTTP.<\/p>\n
Note:<\/strong> Using Option 1<\/strong> codes generally is preferable. The syntax is more expressive, and it will redirect to HTTPS regardless of the port number because the site can technically is able to load with HTTP outside port 80<\/code>.<\/p>\n
\"non-www\" > \"www\" & HTTP > HTTPS<\/h2>\n
If you want to force \"non-www\" to \"www\", and HTTP to HTTPS, then the .htaccess codes above will not suffice.<\/p>\n
To put things into perspective, if your goal is to redirect  the following URLS:<\/p>\n
    \n
  • \n
    http:\/\/www.domain.com<\/code><\/p>\n<\/li>\n
  • \n
    http:\/\/domain.com<\/code><\/p>\n<\/li>\n<\/ul>\n
    to:<\/p>\n
      \n
    • \n
      https<\/strong>:\/\/www.domain.com<\/code><\/p>\n<\/li>\n<\/ul>\n
      Then you will need to use the .htaccess codes below.<\/p>\n
      \r\nRewriteEngine On\r\nRewriteCond %{HTTP_HOST} ^domain.com$ [NC]\r\nRewriteRule (.*) http:\/\/www.domain.com\/$1 [R=301,L]\r\n\r\nRewriteCond %{HTTPS} !on\r\nRewriteRule (.*) https:\/\/%{HTTP_HOST}%{REQUEST_URI}\r\n<\/pre>\n
      Explanation<\/h3>\n
      First, it redirects any \"non-www\" to \"www\",  then it checks for HTTPS, making sure the final result is: www + HTTPS.<\/p>\n
      \"non-www\" > \"www\" & HTTP > HTTPS (in subfolder)<\/h2>\n
      Now, if you are \u2013 like us \u2013 hosting your WordPress website in a subfolder (i.e. www.domain.com\/blog\/<\/code>), then the above mentioned .htaccess codes will not work perfectly.<\/p>\n
      The goal here is to redirect all URLs (regardless if the homepage, or the post pages)  to a www + HTTPS URL.<\/p>\n
      Let\u2019s take a look at all possibilities of URLs that we will need to redirect \u201cfrom<\/em>\u201c, and redirect \u201cto<\/em>\u201c.<\/p>\n
      Condition 1<\/h3>\n
      We need to redirect all the following URLs from:<\/p>\n
        \n
      • \n
        http:\/\/domain.com<\/code><\/p>\n<\/li>\n
      • \n
        http:\/\/www.domain.com<\/code><\/p>\n<\/li>\n
      • \n
        http:\/\/domain.com\/blog\/<\/code><\/p>\n<\/li>\n
      • \n
        http:\/\/www.domain.com\/blog\/<\/code><\/p>\n<\/li>\n<\/ul>\n
        to an unify URL of:<\/p>\n
          \n
        • \n
          https<\/strong>:\/\/www<\/strong>.domain.com\/blog\/<\/code><\/p>\n<\/li>\n<\/ul>\n
          Condition 2<\/h3>\n
          and post URLs from:<\/p>\n
            \n
          • \n
            http:\/\/domain.com\/blog\/example-page\/<\/code><\/p>\n<\/li>\n
          • \n
            http:\/\/www.domain.com\/blog\/example-page\/<\/code><\/p>\n<\/li>\n<\/ul>\n
            to:<\/p>\n
              \n
            • \n
              https<\/strong>:\/\/www<\/strong>.domain.com\/blog\/example-page\/<\/code><\/p>\n<\/li>\n<\/ul>\n
              When your WordPress is hosted in subfolder (E.g. \/blog\/<\/code>), chances are you will have two .htaccess files, I.e. one .htaccess file outside the subfolder, and one inside the subfolder where WordPress is installed. And we will need to alter both of them.<\/p>\n
              \r\n.htaccess\r\nblog\/\r\nblog\/.htaccess\r\n<\/pre>\n
              .htaccess outside subfolder <\/h3>\n
              Insert the following codes into .htaccess outside the subfolder.<\/p>\n
              \r\nRewriteEngine On\r\n### non-www to www, http to https\r\nRewriteCond %{HTTPS} !on\r\nRewriteCond %{HTTP_HOST} ^domain.com$ [OR]\r\nRewriteRule (.*) https:\/\/www.domain.com\/$1 [R=301,L]\r\n\r\n### subfolder\r\nRewriteRule ^$ \/blog\/ [R=301]\r\n<\/pre>\n
              Here\u2019s what this part of the code does. First, it makes sure the domain is redirected to www with HTTPS, then it is redirected to the subfolder. This will satisfy #condition 1 mentioned above but it will not work for condition #2, not yet, at least.<\/p>\n
              .htaccess inside subfolder <\/h3>\n
              Next, we will need to alter the .htaccess code inside the subfolder.<\/p>\n
              By default, it should look something like this:<\/p>\n
              \r\n# BEGIN WordPress\r\n<IfModule mod_rewrite.c>\r\nRewriteEngine On\r\nRewriteBase \/\r\nRewriteRule ^index\\.php$ - [L]\r\nRewriteCond %{REQUEST_FILENAME} !-f\r\nRewriteCond %{REQUEST_FILENAME} !-d\r\nRewriteRule . \/index.php [L]\r\n<\/IfModule>\r\n# END WordPress\r\n<\/pre>\n
              Put the following .htaccess code on top, and before \u201c# BEGIN WordPress\u201d<\/p>\n
              \r\n<IfModule mod_rewrite.c>\r\nRewriteEngine On\r\n## http to https\r\nRewriteCond %{HTTPS} !on\r\nRewriteRule (.*) https:\/\/%{HTTP_HOST}%{REQUEST_URI} [R=301,L]\r\n<\/IfModule>\r\n<\/pre>\n
              With these two set of codes in place, it will ensure any URLs entered will be included with www and HTTPS.<\/p>\n
              I urge that you do not implement this on your live site. Try it out numerous times on a staging\/test site, making sure you\u2019re getting the results you want before deploying it live.<\/p>\n
              One more thing, to ensure your redirecting is accurate, be sure to clear browser cookies and cache before commencing every test.<\/p>","protected":false},"excerpt":{"rendered":"
              You should always load your site with HTTPS. Aside from protecting your data integrity between your websites and your site users, HTTPS is now a requirement for many new browser APIs such as the Geolocation API. HTTPS also carries on some weight in Google SERP ranking signal. So ensuring that your site will always load…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[3400,49],"tags":[4663,252],"topic":[],"class_list":["entry-content","is-maxi"],"acf":[],"yoast_head":"\nForcing HTTP to HTTPS in WordPress (Apache Server) - Hongkiat<\/title>\n<meta name=\"description\" content=\"You should always load your site with HTTPS. Aside from protecting your data integrity between your websites and your site users, HTTPS is now a\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.hongkiat.com\/blog\/force-http-https-wordpress-apache-server\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Forcing HTTP to HTTPS in WordPress (Apache Server)\" \/>\n<meta property=\"og:description\" content=\"You should always load your site with HTTPS. Aside from protecting your data integrity between your websites and your site users, HTTPS is now a\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.hongkiat.com\/blog\/force-http-https-wordpress-apache-server\/\" \/>\n<meta property=\"og:site_name\" content=\"Hongkiat\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/hongkiatcom\" \/>\n<meta property=\"article:published_time\" content=\"2019-11-18T15:32:45+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-10-18T12:12:08+00:00\" \/>\n<meta name=\"author\" content=\"Hongkiat Lim\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@hongkiat\" \/>\n<meta name=\"twitter:site\" content=\"@hongkiat\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Hongkiat Lim\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/force-http-https-wordpress-apache-server\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/force-http-https-wordpress-apache-server\\\/\"},\"author\":{\"name\":\"Hongkiat Lim\",\"@id\":\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/#\\\/schema\\\/person\\\/e3613a3bf757e4f67770f0b7a339edd0\"},\"headline\":\"Forcing HTTP to HTTPS in WordPress (Apache Server)\",\"datePublished\":\"2019-11-18T15:32:45+00:00\",\"dateModified\":\"2022-10-18T12:12:08+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/force-http-https-wordpress-apache-server\\\/\"},\"wordCount\":627,\"publisher\":{\"@id\":\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/#organization\"},\"keywords\":[\"ad-divi\",\"WordPress Tips\"],\"articleSection\":[\"Hosting\",\"WordPress\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/force-http-https-wordpress-apache-server\\\/\",\"url\":\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/force-http-https-wordpress-apache-server\\\/\",\"name\":\"Forcing HTTP to HTTPS in WordPress (Apache Server) - Hongkiat\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/#website\"},\"datePublished\":\"2019-11-18T15:32:45+00:00\",\"dateModified\":\"2022-10-18T12:12:08+00:00\",\"description\":\"You should always load your site with HTTPS. Aside from protecting your data integrity between your websites and your site users, HTTPS is now a\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/force-http-https-wordpress-apache-server\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/force-http-https-wordpress-apache-server\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/force-http-https-wordpress-apache-server\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Forcing HTTP to HTTPS in WordPress (Apache Server)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/\",\"name\":\"Hongkiat\",\"description\":\"Tech and Design Tips\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/#organization\",\"name\":\"Hongkiat.com\",\"url\":\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/wp-content\\\/uploads\\\/hkdc-logo-rect-yoast.jpg\",\"contentUrl\":\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/wp-content\\\/uploads\\\/hkdc-logo-rect-yoast.jpg\",\"width\":1200,\"height\":799,\"caption\":\"Hongkiat.com\"},\"image\":{\"@id\":\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/hongkiatcom\",\"https:\\\/\\\/x.com\\\/hongkiat\",\"https:\\\/\\\/www.pinterest.com\\\/hongkiat\\\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/#\\\/schema\\\/person\\\/e3613a3bf757e4f67770f0b7a339edd0\",\"name\":\"Hongkiat Lim\",\"description\":\"Founder and Editor in Chief of Hongkiat.com. Hongkiat is also a designer, developer, entrepreneur, and an active investor in the US stock market.\",\"sameAs\":[\"http:\\\/\\\/www.hongkiat.com\\\/blog\"],\"url\":\"https:\\\/\\\/www.hongkiat.com\\\/blog\\\/author\\\/hongkiat\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Forcing HTTP to HTTPS in WordPress (Apache Server) - Hongkiat","description":"You should always load your site with HTTPS. Aside from protecting your data integrity between your websites and your site users, HTTPS is now a","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.hongkiat.com\/blog\/force-http-https-wordpress-apache-server\/","og_locale":"en_US","og_type":"article","og_title":"Forcing HTTP to HTTPS in WordPress (Apache Server)","og_description":"You should always load your site with HTTPS. Aside from protecting your data integrity between your websites and your site users, HTTPS is now a","og_url":"https:\/\/www.hongkiat.com\/blog\/force-http-https-wordpress-apache-server\/","og_site_name":"Hongkiat","article_publisher":"https:\/\/www.facebook.com\/hongkiatcom","article_published_time":"2019-11-18T15:32:45+00:00","article_modified_time":"2022-10-18T12:12:08+00:00","author":"Hongkiat Lim","twitter_card":"summary_large_image","twitter_creator":"@hongkiat","twitter_site":"@hongkiat","twitter_misc":{"Written by":"Hongkiat Lim","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.hongkiat.com\/blog\/force-http-https-wordpress-apache-server\/#article","isPartOf":{"@id":"https:\/\/www.hongkiat.com\/blog\/force-http-https-wordpress-apache-server\/"},"author":{"name":"Hongkiat Lim","@id":"https:\/\/www.hongkiat.com\/blog\/#\/schema\/person\/e3613a3bf757e4f67770f0b7a339edd0"},"headline":"Forcing HTTP to HTTPS in WordPress (Apache Server)","datePublished":"2019-11-18T15:32:45+00:00","dateModified":"2022-10-18T12:12:08+00:00","mainEntityOfPage":{"@id":"https:\/\/www.hongkiat.com\/blog\/force-http-https-wordpress-apache-server\/"},"wordCount":627,"publisher":{"@id":"https:\/\/www.hongkiat.com\/blog\/#organization"},"keywords":["ad-divi","WordPress Tips"],"articleSection":["Hosting","WordPress"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.hongkiat.com\/blog\/force-http-https-wordpress-apache-server\/","url":"https:\/\/www.hongkiat.com\/blog\/force-http-https-wordpress-apache-server\/","name":"Forcing HTTP to HTTPS in WordPress (Apache Server) - Hongkiat","isPartOf":{"@id":"https:\/\/www.hongkiat.com\/blog\/#website"},"datePublished":"2019-11-18T15:32:45+00:00","dateModified":"2022-10-18T12:12:08+00:00","description":"You should always load your site with HTTPS. Aside from protecting your data integrity between your websites and your site users, HTTPS is now a","breadcrumb":{"@id":"https:\/\/www.hongkiat.com\/blog\/force-http-https-wordpress-apache-server\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.hongkiat.com\/blog\/force-http-https-wordpress-apache-server\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.hongkiat.com\/blog\/force-http-https-wordpress-apache-server\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.hongkiat.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Forcing HTTP to HTTPS in WordPress (Apache Server)"}]},{"@type":"WebSite","@id":"https:\/\/www.hongkiat.com\/blog\/#website","url":"https:\/\/www.hongkiat.com\/blog\/","name":"Hongkiat","description":"Tech and Design Tips","publisher":{"@id":"https:\/\/www.hongkiat.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.hongkiat.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.hongkiat.com\/blog\/#organization","name":"Hongkiat.com","url":"https:\/\/www.hongkiat.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.hongkiat.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.hongkiat.com\/blog\/wp-content\/uploads\/hkdc-logo-rect-yoast.jpg","contentUrl":"https:\/\/www.hongkiat.com\/blog\/wp-content\/uploads\/hkdc-logo-rect-yoast.jpg","width":1200,"height":799,"caption":"Hongkiat.com"},"image":{"@id":"https:\/\/www.hongkiat.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/hongkiatcom","https:\/\/x.com\/hongkiat","https:\/\/www.pinterest.com\/hongkiat\/"]},{"@type":"Person","@id":"https:\/\/www.hongkiat.com\/blog\/#\/schema\/person\/e3613a3bf757e4f67770f0b7a339edd0","name":"Hongkiat Lim","description":"Founder and Editor in Chief of Hongkiat.com. Hongkiat is also a designer, developer, entrepreneur, and an active investor in the US stock market.","sameAs":["http:\/\/www.hongkiat.com\/blog"],"url":"https:\/\/www.hongkiat.com\/blog\/author\/hongkiat\/"}]}},"jetpack_featured_media_url":"https:\/\/","jetpack_shortlink":"https:\/\/wp.me\/p4uxU-cKY","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.hongkiat.com\/blog\/wp-json\/wp\/v2\/posts\/49040","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.hongkiat.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.hongkiat.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.hongkiat.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.hongkiat.com\/blog\/wp-json\/wp\/v2\/comments?post=49040"}],"version-history":[{"count":1,"href":"https:\/\/www.hongkiat.com\/blog\/wp-json\/wp\/v2\/posts\/49040\/revisions"}],"predecessor-version":[{"id":49041,"href":"https:\/\/www.hongkiat.com\/blog\/wp-json\/wp\/v2\/posts\/49040\/revisions\/49041"}],"wp:attachment":[{"href":"https:\/\/www.hongkiat.com\/blog\/wp-json\/wp\/v2\/media?parent=49040"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.hongkiat.com\/blog\/wp-json\/wp\/v2\/categories?post=49040"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.hongkiat.com\/blog\/wp-json\/wp\/v2\/tags?post=49040"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/www.hongkiat.com\/blog\/wp-json\/wp\/v2\/topic?post=49040"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}