{"id":38395,"date":"2025-09-08T14:38:52","date_gmt":"2025-09-08T19:38:52","guid":{"rendered":"https:\/\/www.webstix.com\/?p=38395"},"modified":"2025-09-08T14:38:52","modified_gmt":"2025-09-08T19:38:52","slug":"ai-didnt-kill-seo","status":"publish","type":"post","link":"https:\/\/staging.webstix.net\/WSX\/wp\/the-webstix-blog\/ai-didnt-kill-seo\/","title":{"rendered":"AI Didn\u2019t Quite Kill SEO: What Local Businesses Should Actually Do in 2025"},"content":{"rendered":"<p><img fetchpriority=\"high\" decoding=\"async\" class=\"aligncenter size-large wp-image-38397\" src=\"http:\/\/www.webstix.com\/wp-content\/uploads\/2025\/09\/ai-didnt-quite-kill-seo-1024x585.jpg\" alt=\"Clean, modern hero image showing that \u2018AI didn\u2019t kill SEO\u2019 for local businesses. A laptop browser mockup displays a page with bold Q&amp;A headings and a short 40\u201360 word answer block.\" width=\"1024\" height=\"585\"><\/p>\n<div style=\"border: 1px solid #e5e7eb;padding: 16px;border-radius: 8px;background: #f9fafb;margin: 18px 0\"><strong>TL;DR:<\/strong> Stop chasing \u201cAI triggers.\u201d Answer real questions at the top, format for snippets and voice, add the right schema, build hyper-local clusters, and run one micro test every week. That mix still wins.<\/div>\n<p><!-- H2 --><\/p>\n<h2>Myth #1: You need special \u201cAI keywords\u201d<\/h2>\n<p>People try to force AI responses by sprinkling magic phrases across pages. That misses the point. AI and modern search line up with questions and intent. If someone types \u201cHow long does SEO take?\u201d they want a straight answer in the first sentence. They do not want a lecture about search history.<\/p>\n<p>Pages you make now need to get to the point ASAP &#8211; no dancing around the topic at all. Give people the answer. One, great way is with a TL;DR block at the top of pages. Boil it all down. Here&#8217;s more&#8230;<\/p>\n<p><!-- H3 --><\/p>\n<h3>What to do instead<\/h3>\n<ul>\n<li>List the top five questions customers actually ask on calls and in emails.<\/li>\n<li>Make each question an H2. Put a one-sentence answer immediately under it.<\/li>\n<li>Follow with a short \u201cit depends\u201d section, then give one clear next step.<\/li>\n<\/ul>\n<p><em>Example:<\/em> A dentist in Nashville\u2019s 12 South neighborhood writes \u201cHow soon can I get a crown?\u201d as an H2 with a one-sentence answer first. That clean format gets saved, quoted, and read aloud by assistants more often than a wall of text.<\/p>\n<p><!-- H2 --><\/p>\n<h2>Myth #2: Featured snippets are dead because of AI overviews<\/h2>\n<p>Desktop clicks on snippets can dip when an AI box shows up. That does not make snippets useless. Snippets still feed voice assistants and quick mobile answers. Those users are often closer to taking action.<\/p>\n<p><!-- H3 --><\/p>\n<h3>What to do instead<\/h3>\n<ul>\n<li>Use <strong>question headings<\/strong> followed by a <strong>standalone 40\u201360 word paragraph<\/strong>.<\/li>\n<li>Answer first. Add detail after. Write something that could be read aloud clearly.<\/li>\n<li>Where it helps, add a short list of three to five steps or pros and cons.<\/li>\n<\/ul>\n<p><em>Example:<\/em> An electrician in Madison\u2019s Downtown area creates a \u201cDo I need a permit to add outlets?\u201d blog post with that question as an H1 with a crisp answer and a 3-bullet checklist. That&#8217;s perfect for snippets and voice.<\/p>\n<p><!-- H2 --><\/p>\n<h2>Myth #3: Schema markup does not matter anymore<\/h2>\n<p>Schema is how machines understand your page types and sections. For Q&amp;A and step-by-step content, it is a shortcut to clarity. Not because it hacks the system, but because it labels your content properly. <strong>Your website isn&#8217;t just serving one audience now, but also your audience through AI.<\/strong><\/p>\n<p><!-- H3 --><\/p>\n<h3>What to do instead<\/h3>\n<ul>\n<li>Add <strong>FAQPage<\/strong> schema to your main FAQ page. Map three to eight real questions.<\/li>\n<li>Add <strong>HowTo<\/strong> schema to any step-by-step process like installations, maintenance, or estimate steps.<\/li>\n<li>Keep <strong>LocalBusiness<\/strong> details accurate: name, address, phone, hours, and service areas.<\/li>\n<\/ul>\n<p><em>Example:<\/em> An HVAC company in Rockford\u2019s north side area publishes \u201cHow to change a 1-inch filter\u201d with HowTo schema and a 60-second video. That page becomes the internal link target anytime filters are mentioned on the site.<\/p>\n<hr>\n<p><!-- BEGIN: AI Tech Readiness Section --><!-- H2 --><\/p>\n<h2>Get Your Site Technically Ready for AI (Beyond Schema)<\/h2>\n<p>Answer-first content is the foundation, but machines also need clean, machine-readable signals. Here\u2019s how to make your site easier for AI systems to understand and cite.<\/p>\n<p><!-- H3 --><\/p>\n<h3>1) Clean, crawlable signals<\/h3>\n<ul>\n<li><strong>Canonical URLs:<\/strong> One preferred URL per page. Set canonicals correctly on variants (with\/without params, print pages, tracking URLs).<\/li>\n<li><strong>Indexing hygiene:<\/strong> Use <code>&lt;meta name=\"robots\" content=\"index,follow\"&gt;<\/code> (or <code>noindex<\/code> when needed). Avoid blocking important pages in <code>robots.txt<\/code>.<\/li>\n<li><strong>Sitemaps:<\/strong> Keep XML sitemaps fresh. Include service pages, FAQs, and any critical guides. Regenerate on publish\/update.<\/li>\n<li><strong>Core Web Vitals and mobile:<\/strong> Fast LCP, stable CLS, quick TTFB. If a phone struggles to render your page, assistants will, too.<\/li>\n<li><strong>Consistent NAP:<\/strong> Name, address, phone, hours must match across your site, schema, and major listings.<\/li>\n<\/ul>\n<p><!-- H3 --><\/p>\n<h3>2) JSON-LD that helps machines \u201csee\u201d your business<\/h3>\n<p>Beyond FAQPage and HowTo, add the basics that describe who you are, where you operate, and what you offer.<\/p>\n<ul>\n<li><strong>LocalBusiness:<\/strong> Include <code>address<\/code>, <code>geo<\/code> (if storefront), <code>openingHoursSpecification<\/code>, <code>areaServed<\/code>, <code>telephone<\/code>, <code>sameAs<\/code> (major profiles).<\/li>\n<li><strong>Service<\/strong> (on service pages): Define what you do, typical areas served, and link back to your LocalBusiness entity with <code>provider<\/code>.<\/li>\n<li><strong>BreadcrumbList:<\/strong> Helps AIs understand page position in your site structure.<\/li>\n<li><strong>WebSite + SearchAction:<\/strong> Lets assistants discover your internal search endpoint.<\/li>\n<\/ul>\n<p><!-- Example JSON-LD (edit values, keep structure) --><\/p>\n<p>\n{<br \/>\n  &#8220;@context&#8221;: &#8220;https:\/\/schema.org&#8221;,<br \/>\n  &#8220;@type&#8221;: &#8220;LocalBusiness&#8221;,<br \/>\n  &#8220;name&#8221;: &#8220;Example Plumbing Co.&#8221;,<br \/>\n  &#8220;url&#8221;: &#8220;https:\/\/www.exampleplumbing.com\/&#8221;,<br \/>\n  &#8220;telephone&#8221;: &#8220;+1-555-123-4567&#8221;,<br \/>\n  &#8220;image&#8221;: &#8220;https:\/\/www.exampleplumbing.com\/assets\/brand.jpg&#8221;,<br \/>\n  &#8220;address&#8221;: {<br \/>\n    &#8220;@type&#8221;: &#8220;PostalAddress&#8221;,<br \/>\n    &#8220;streetAddress&#8221;: &#8220;1234 W Oak St&#8221;,<br \/>\n    &#8220;addressLocality&#8221;: &#8220;Austin&#8221;,<br \/>\n    &#8220;addressRegion&#8221;: &#8220;TX&#8221;,<br \/>\n    &#8220;postalCode&#8221;: &#8220;78704&#8221;,<br \/>\n    &#8220;addressCountry&#8221;: &#8220;US&#8221;<br \/>\n  },<br \/>\n  &#8220;openingHoursSpecification&#8221;: [<br \/>\n    {<br \/>\n      &#8220;@type&#8221;: &#8220;OpeningHoursSpecification&#8221;,<br \/>\n      &#8220;dayOfWeek&#8221;: [&#8220;Monday&#8221;,&#8221;Tuesday&#8221;,&#8221;Wednesday&#8221;,&#8221;Thursday&#8221;,&#8221;Friday&#8221;],<br \/>\n      &#8220;opens&#8221;: &#8220;07:30&#8221;,<br \/>\n      &#8220;closes&#8221;: &#8220;18:00&#8221;<br \/>\n    }<br \/>\n  ],<br \/>\n  &#8220;areaServed&#8221;: [<br \/>\n    {&#8220;@type&#8221;:&#8221;AdministrativeArea&#8221;,&#8221;name&#8221;:&#8221;Zilker&#8221;},<br \/>\n    {&#8220;@type&#8221;:&#8221;AdministrativeArea&#8221;,&#8221;name&#8221;:&#8221;Barton Hills&#8221;},<br \/>\n    {&#8220;@type&#8221;:&#8221;AdministrativeArea&#8221;,&#8221;name&#8221;:&#8221;Travis Heights&#8221;}<br \/>\n  ],<br \/>\n  &#8220;sameAs&#8221;: [<br \/>\n    &#8220;https:\/\/www.facebook.com\/exampleplumbing&#8221;,<br \/>\n    &#8220;https:\/\/www.instagram.com\/exampleplumbing&#8221;<br \/>\n  ]<br \/>\n}<\/p>\n<p>{<br \/>\n  &#8220;@context&#8221;: &#8220;https:\/\/schema.org&#8221;,<br \/>\n  &#8220;@type&#8221;: &#8220;WebSite&#8221;,<br \/>\n  &#8220;url&#8221;: &#8220;https:\/\/www.exampleplumbing.com\/&#8221;,<br \/>\n  &#8220;potentialAction&#8221;: {<br \/>\n    &#8220;@type&#8221;: &#8220;SearchAction&#8221;,<br \/>\n    &#8220;target&#8221;: &#8220;https:\/\/www.exampleplumbing.com\/search?q={search_term_string}&#8221;,<br \/>\n    &#8220;query-input&#8221;: &#8220;required name=search_term_string&#8221;<br \/>\n  }<br \/>\n}\n<\/p>\n<p><!-- H3 --><\/p>\n<h3>3) Machine-readable JSON for key actions (forms, hours, locations)<\/h3>\n<p>In addition to JSON-LD, offer simple JSON endpoints that describe forms and business data. This helps assistants and integrations understand how to contact you or submit a lead without guessing your HTML.<\/p>\n<ul>\n<li><strong>Publish lightweight JSON endpoints<\/strong> like <code>\/hours.json<\/code>, <code>\/contact.json<\/code>, and <code>\/locations.json<\/code>.<\/li>\n<li><strong>Keep them stable<\/strong> and versioned if you evolve the format (for example, <code>\/contact.v1.json<\/code>).<\/li>\n<li><strong>Allow CORS<\/strong> for <code>GET<\/code> on these endpoints so trusted clients can read them.<\/li>\n<\/ul>\n<p><!-- Example: \/contact.json (plain JSON, not JSON-LD) --><\/p>\n<pre><code>{\n  \"name\": \"Website Contact\",\n  \"method\": \"POST\",\n  \"action\": \"https:\/\/www.exampleplumbing.com\/wp-json\/webstix\/v1\/contact\",\n  \"fields\": [\n    {\"name\":\"name\",\"type\":\"text\",\"required\":true,\"label\":\"Your Name\"},\n    {\"name\":\"email\",\"type\":\"email\",\"required\":true,\"label\":\"Email\"},\n    {\"name\":\"phone\",\"type\":\"tel\",\"required\":false,\"label\":\"Phone\"},\n    {\"name\":\"service\",\"type\":\"select\",\"required\":true,\"options\":[\"Drain Cleaning\",\"Water Heater\",\"Burst Pipe\"]},\n    {\"name\":\"message\",\"type\":\"textarea\",\"required\":true,\"minLength\":20}\n  ],\n  \"validation\": {\n    \"honeypotField\":\"company\",\n    \"rateLimitPerIP\":\"10\/hour\"\n  },\n  \"success\": {\n    \"message\":\"Thanks\u2014our team will reach out shortly.\",\n    \"redirect\": \"https:\/\/www.exampleplumbing.com\/thank-you\/\"\n  }\n}<\/code><\/pre>\n<p><!-- Example: \/hours.json --><\/p>\n<pre><code>{\n  \"timezone\": \"America\/Chicago\",\n  \"regular\": [\n    {\"day\":\"Mon-Fri\",\"opens\":\"07:30\",\"closes\":\"18:00\"},\n    {\"day\":\"Sat\",\"opens\":\"09:00\",\"closes\":\"13:00\"}\n  ],\n  \"exceptions\": [\n    {\"date\":\"2025-11-27\",\"closed\":true,\"note\":\"Thanksgiving\"}\n  ]\n}<\/code><\/pre>\n<p><em>Why this helps:<\/em> Assistants can fetch your hours, know which fields your form expects, and submit or hand off leads correctly. You are reducing ambiguity and making it easier to cite or transact.<\/p>\n<p><!-- H3 --><\/p>\n<h3>4) Action patterns for assistants<\/h3>\n<ul>\n<li><strong>ContactAction:<\/strong> In JSON-LD, describe how to contact you with a target EntryPoint. Keep it accurate with your real contact URL.<\/li>\n<li><strong>Book an estimate:<\/strong> If you offer bookings, describe the flow with an <code>Action<\/code> type that points to your booking page or API.<\/li>\n<\/ul>\n<p><!-- Example JSON-LD ContactAction (attach to Organization or LocalBusiness) --><\/p>\n<p>\n{<br \/>\n  &#8220;@context&#8221;:&#8221;https:\/\/schema.org&#8221;,<br \/>\n  &#8220;@type&#8221;:&#8221;LocalBusiness&#8221;,<br \/>\n  &#8220;name&#8221;:&#8221;Example Plumbing Co.&#8221;,<br \/>\n  &#8220;url&#8221;:&#8221;https:\/\/www.exampleplumbing.com\/&#8221;,<br \/>\n  &#8220;potentialAction&#8221;:{<br \/>\n    &#8220;@type&#8221;:&#8221;ContactAction&#8221;,<br \/>\n    &#8220;target&#8221;:{<br \/>\n      &#8220;@type&#8221;:&#8221;EntryPoint&#8221;,<br \/>\n      &#8220;urlTemplate&#8221;:&#8221;https:\/\/www.exampleplumbing.com\/contact\/&#8221;,<br \/>\n      httpMethod&#8221;:&#8221;POST<br \/>\n    }<br \/>\n  }<br \/>\n}\n<\/p>\n<p><!-- H3 --><\/p>\n<h3>5) Practical extras that reduce friction<\/h3>\n<ul>\n<li><strong>Accessible markup:<\/strong> Labels tied to inputs, descriptive alt text, clear focus states. If screen readers can parse it, AIs generally can, too.<\/li>\n<li><strong>Server responses:<\/strong> Return proper HTTP codes on forms and APIs. 200 for success, 4xx for validation errors with a concise JSON error body.<\/li>\n<li><strong>Security and trust:<\/strong> Valid TLS, HSTS, and visible contact options. Don\u2019t gate essential info behind heavy JS.<\/li>\n<li><strong>Consistent CTAs:<\/strong> Phone numbers in <code>tel:<\/code> links, emails in <code>mailto:<\/code>, and addresses with <code>geo<\/code> in JSON-LD.<\/li>\n<\/ul>\n<p><strong>Bottom line:<\/strong> Keep your human content clear, and give machines predictable, structured hooks. That combo is what gets surfaced and cited.<\/p>\n<p><!-- END: AI Tech Readiness Section --><\/p>\n<hr>\n<p><!-- H2 --><\/p>\n<h2>Shift #1: Hyper-local content clusters beat generic city pages<\/h2>\n<p>Citywide pages like \u201cMadison Roofing\u201d still help, but they lose to pages built for specific neighborhoods and micro areas. Think landmarks, subdivisions, campus zones, and real problems locals face.<\/p>\n<p><!-- H3 --><\/p>\n<h3>How to build a hyper-local cluster<\/h3>\n<ol>\n<li><strong>Pick four to six micro areas<\/strong> you truly serve. For Denver, that could be Cherry Creek, Washington Park, Green Valley Ranch, Sloan\u2019s Lake.<\/li>\n<li><strong>Create a dedicated page<\/strong> for each with details that prove you know the area:\n<ul>\n<li>Common jobs in that area like flat roofs, alley access, older brick chimneys.<\/li>\n<li>Local constraints like HOA quirks, permit rules, parking, or narrow streets.<\/li>\n<li>Response times and seasonal notes like hail cycles or freeze and thaw.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Interlink<\/strong> these pages from your main service page and an \u201cAreas We Serve\u201d footer block.<\/li>\n<\/ol>\n<p><em>Example:<\/em> A plumber in Eau Claire\u2019s west side mentions older multi-family buildings, UW-Eau Claire&#8217;s move-in weeks, and common winter pipe bursts. That level of detail wins \u201cnear me\u201d and campus searches a generic \u201cEau Claire plumber\u201d page will not reach.<\/p>\n<p><!-- H2 --><\/p>\n<h2>Shift #2: Continuous micro A\/B testing, every week<\/h2>\n<p>Search changes fast. Quarterly tests are too slow. You do not need giant experiments. One controlled tweak per week is enough if you track it.<\/p>\n<p><!-- H3 --><\/p>\n<h3>A 30-minute weekly testing loop<\/h3>\n<ol>\n<li><strong>Pick one micro test<\/strong>: headline variant, a tighter first sentence, bullets vs paragraph, a mini-FAQ add, or a different hero CTA.<\/li>\n<li><strong>Ship one change<\/strong> on one page. Do not bundle five changes at once.<\/li>\n<li><strong>Track<\/strong> impressions, clicks, snippet pickup, and conversions for two to three weeks.<\/li>\n<li><strong>Roll out the winner<\/strong> to similar pages.<\/li>\n<\/ol>\n<p><em>Example micro tests:<\/em> \u201cHow long does a heat pump last?\u201d Try a one-sentence answer vs a three-sentence answer. \u201cSump pump failure signs\u201d Try bullets first vs a paragraph first. \u201cEmergency roofer near McFarland\u201d Try a phone-first CTA vs a form-first CTA.<\/p>\n<p><!-- H2 --><\/p>\n<h2>Implementation checklist<\/h2>\n<ul>\n<li>Refresh five Q&amp;A sections with the answer in sentence one.<\/li>\n<li>Add <strong>HowTo<\/strong> schema to one process page and <strong>FAQPage<\/strong> schema to your main FAQ.<\/li>\n<li>Publish three to five hyper-local pages with real, unique details.<\/li>\n<li>Start a simple weekly test log. One change, one page, one metric.<\/li>\n<li>Link new local pages from your main services and your footer.<\/li>\n<\/ul>\n<p><!-- H2 --><\/p>\n<h2>Real-world ideas you can borrow<\/h2>\n<ul>\n<li><strong>Ann Arbor near South Quad:<\/strong> \u201cSame-day drain clearing near campus\u201d with map, campus hours, and a phone CTA during move-in weeks.<\/li>\n<li><strong>Columbus Short North:<\/strong> \u201cSmall storefront signage permits\u201d with a 5-step HowTo and links to city forms.<\/li>\n<li><strong>Austin Zilker:<\/strong> \u201cMini-split installs in older bungalows\u201d that covers attic access, power constraints, and typical timelines.<\/li>\n<\/ul>\n<p><!-- H2 --><\/p>\n<hr>\n<h2>FAQs About AI and SEO for Small Businesses<\/h2>\n<h3>Are AI overviews replacing websites?<\/h3>\n<p>No. They shift where attention goes. Pages that answer questions cleanly, use schema, and cover specific neighborhoods still win traffic and leads.<\/p>\n<h3>Do I need a separate page for every suburb?<\/h3>\n<p>No. Start with three to five you truly serve and can write about in a useful way. Add more only if you have real details.<\/p>\n<h3>What should I test first?<\/h3>\n<p>Test the first sentence on your most searched question page. Make it a direct, quotable answer. That single change often moves the needle.<\/p>\n<p><!-- H2 --><\/p>\n<h2>Next steps<\/h2>\n<p>Pick one: publish a hyper-local page this week, add FAQPage schema to your FAQ, or run your first micro test. Do one of those every week for a month and you will feel the difference in both visibility and lead quality.<\/p>\n<p>Do you&#8230; need help with that? We&#8217;d be happy to help you get started and get your website more in tune with AI. <a href=\"https:\/\/staging.webstix.net\/WSX\/wp\/contact-us\/\">Contact Webstix today<\/a> to get going.<\/p>\n<p>\n{<br \/>\n  &#8220;@context&#8221;: &#8220;https:\/\/schema.org&#8221;,<br \/>\n  &#8220;@type&#8221;: &#8220;FAQPage&#8221;,<br \/>\n  &#8220;mainEntity&#8221;: [<br \/>\n    {<br \/>\n      &#8220;@type&#8221;: &#8220;Question&#8221;,<br \/>\n      &#8220;name&#8221;: &#8220;Are AI overviews replacing websites?&#8221;,<br \/>\n      &#8220;acceptedAnswer&#8221;: {<br \/>\n        &#8220;@type&#8221;: &#8220;Answer&#8221;,<br \/>\n        &#8220;text&#8221;: &#8220;No. They shift where attention goes. Pages that answer questions cleanly, use schema, and cover specific neighborhoods still win traffic and leads.&#8221;<br \/>\n      }<br \/>\n    },<br \/>\n    {<br \/>\n      &#8220;@type&#8221;: &#8220;Question&#8221;,<br \/>\n      &#8220;name&#8221;: &#8220;Do I need a separate page for every suburb?&#8221;,<br \/>\n      &#8220;acceptedAnswer&#8221;: {<br \/>\n        &#8220;@type&#8221;: &#8220;Answer&#8221;,<br \/>\n        &#8220;text&#8221;: &#8220;No. Start with three to five you truly serve and can write about in a useful way. Add more only if you have real details.&#8221;<br \/>\n      }<br \/>\n    },<br \/>\n    {<br \/>\n      &#8220;@type&#8221;: &#8220;Question&#8221;,<br \/>\n      &#8220;name&#8221;: &#8220;What should I test first?&#8221;,<br \/>\n      &#8220;acceptedAnswer&#8221;: {<br \/>\n        &#8220;@type&#8221;: &#8220;Answer&#8221;,<br \/>\n        &#8220;text&#8221;: &#8220;Test the first sentence on your most searched question page. Make it a direct, quotable answer. That single change often moves the needle.&#8221;<br \/>\n      }<br \/>\n    }<br \/>\n  ]<br \/>\n}<\/p>\n","protected":false},"excerpt":{"rendered":"<p>TL;DR: Stop chasing \u201cAI triggers.\u201d Answer real questions at the top, format for snippets and voice, add the right schema, build hyper-local clusters, and run one micro test every week. That mix still wins. Myth #1: You need special \u201cAI keywords\u201d People try to force AI responses by sprinkling magic phrases across pages. That misses [&hellip;]<\/p>\n","protected":false},"author":468,"featured_media":190694,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"_tldrpress_summary":"","_tldrpress_summary_type":"","_tldrpress_summary_length":"","footnotes":""},"categories":[3],"tags":[],"class_list":["post-38395","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-the-webstix-blog"],"acf":[],"_links":{"self":[{"href":"https:\/\/staging.webstix.net\/WSX\/wp\/wp-json\/wp\/v2\/posts\/38395","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/staging.webstix.net\/WSX\/wp\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/staging.webstix.net\/WSX\/wp\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/staging.webstix.net\/WSX\/wp\/wp-json\/wp\/v2\/users\/468"}],"replies":[{"embeddable":true,"href":"https:\/\/staging.webstix.net\/WSX\/wp\/wp-json\/wp\/v2\/comments?post=38395"}],"version-history":[{"count":0,"href":"https:\/\/staging.webstix.net\/WSX\/wp\/wp-json\/wp\/v2\/posts\/38395\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/staging.webstix.net\/WSX\/wp\/wp-json\/wp\/v2\/media\/190694"}],"wp:attachment":[{"href":"https:\/\/staging.webstix.net\/WSX\/wp\/wp-json\/wp\/v2\/media?parent=38395"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/staging.webstix.net\/WSX\/wp\/wp-json\/wp\/v2\/categories?post=38395"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/staging.webstix.net\/WSX\/wp\/wp-json\/wp\/v2\/tags?post=38395"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}