{"id":265278,"date":"2026-07-07T08:30:00","date_gmt":"2026-07-06T23:30:00","guid":{"rendered":"https:\/\/designcopy.net\/en\/?p=265278"},"modified":"2026-07-07T09:26:31","modified_gmt":"2026-07-07T00:26:31","slug":"ga4-track-chatgpt-perplexity-gemini-ai-traffic","status":"publish","type":"post","link":"https:\/\/designcopy.net\/en\/ga4-track-chatgpt-perplexity-gemini-ai-traffic\/","title":{"rendered":"GA4&#8217;s New AI Assistant Channel: How to Track ChatGPT, Perplexity, and Gemini Traffic in 2026"},"content":{"rendered":"<h1>GA4&#8217;s New AI Assistant Channel: How to Track ChatGPT, Perplexity, and Gemini Traffic in 2026<\/h1>\n<div style=\"background:#e3f2fd;border-left:4px solid #1976d2;padding:16px 20px;margin:20px 0;border-radius:4px;\">\n<strong style=\"color:#0d47a1;font-size:1.1em;\">Quick Answer:<\/strong><\/p>\n<ul>\n<li><strong>What changed:<\/strong> On May 13, 2026, Google added a native &#8220;AI Assistant&#8221; default channel group to GA4 that auto-classifies traffic from recognized chatbots like ChatGPT, Gemini, and <a href=\"https:\/\/en.wikipedia.org\/wiki\/Claude_(language_model)\" target=\"_blank\" rel=\"noopener nofollow external noreferrer\" data-wpel-link=\"external\">Claude<\/a>.<\/li>\n<li><strong>Why you still need a regex filter:<\/strong> The native channel misses newer or unrecognized AI hosts, and Google AI Overviews traffic still arrives as plain organic search.<\/li>\n<li><strong>The fix:<\/strong> Build a custom channel group named &#8220;AI Tools&#8221; with a Source <em>matches regex<\/em> condition, and drag it above Referral so AI sessions are intercepted first.<\/li>\n<li><strong>What to measure:<\/strong> Compare AI Assistant sessions against your conversions in Explore reports to see whether ChatGPT and Perplexity visitors actually convert.<\/li>\n<\/ul>\n<\/div>\n<p>You optimized a page to get cited by ChatGPT and Perplexity. The citations are showing up. So where is that traffic in your reports?<\/p>\n<p>For most of 2025 and early 2026, the honest answer was &#8220;hidden.&#8221; AI visits landed in the Referral or Direct buckets, mixed in with everything else.<\/p>\n<p>That changed in May 2026. This guide covers what GA4 now tracks automatically, the regex backfill you still need, and how to tie AI visits to real conversions.<\/p>\n<h2>What changed in GA4 for AI traffic in May 2026?<\/h2>\n<p>Google added a native &#8220;AI Assistant&#8221; default channel group to GA4 on May 13, 2026.<\/p>\n<p>Per <a href=\"https:\/\/support.google.com\/analytics\/answer\/9756891\" target=\"_blank\" rel=\"noopener nofollow external noreferrer\" data-wpel-link=\"external\">Google&#8217;s Analytics Help documentation<\/a>, the channel automatically groups sessions from recognized AI chatbot referrers, with ChatGPT, Gemini, and Claude named as examples. It works across every property without setup.<\/p>\n<p>Before this, every chatbot click was filed as Referral or Direct. Now a separate row finally isolates the trend.<\/p>\n<div style=\"background:#e8f5e9;border-left:4px solid #43a047;padding:16px 20px;margin:20px 0;border-radius:4px;\">\n<strong style=\"color:#1b5e20;\">Pro Tip:<\/strong> Check Reports &gt; Acquisition &gt; Traffic acquisition and switch the dimension to &#8220;Session default channel group.&#8221; If &#8220;AI Assistant&#8221; is missing, your property may not have refreshed yet. A custom channel group, covered below, gives you the same view immediately and on your own terms.<\/div>\n<figure style=\"margin:24px 0;text-align:center;\"><img decoding=\"async\" src=\"https:\/\/designcopy.net\/wp-content\/uploads\/2026\/06\/ga4-track-chatgpt-perplexity-gemini-ai-traffic-internal-1-hero.jpg\" alt=\"What changed in GA4 for AI traffic in May 2026?\" style=\"max-width:100%;height:auto;border-radius:8px;\" loading=\"lazy\" title=\"\"><\/figure>\n<h2>Why was AI traffic invisible in GA4 before this update?<\/h2>\n<p>AI visits were invisible because GA4 had no bucket for them, so it sorted them by referrer header instead.<\/p>\n<p>When an AI platform passes a referrer header, GA4 files the session as Referral and buries it among dozens of other referring domains. You would see a faint &#8220;chatgpt.com \/ referral&#8221; row and little else.<\/p>\n<p>When the referrer header is stripped, the session lands in Direct. This happens often with desktop apps and privacy-focused browser settings, which means a real chunk of AI traffic looked like people typing your URL from memory.<\/p>\n<div style=\"background:#fff3e0;border-left:4px solid #fb8c00;padding:16px 20px;margin:20px 0;border-radius:4px;\">\n<strong style=\"color:#e65100;\">Warning:<\/strong> Google AI Overviews traffic is not the same as chatbot traffic. When someone clicks a link inside an AI Overview, the referrer is still google.com\/search, so it stays inside your Organic Search numbers. No channel group, native or custom, can split it out. Treat AI Overview clicks as part of organic, not as a separate AI line.<\/div>\n<p>The table below shows where each source lands by default before you build anything custom.<\/p>\n<table style=\"width:100%;border-collapse:collapse;margin:20px 0;\">\n<thead>\n<tr style=\"background:#1a237e;color:#fff;\">\n<th style=\"padding:10px;text-align:left;border:1px solid #ccc;\">AI source<\/th>\n<th style=\"padding:10px;text-align:left;border:1px solid #ccc;\">Typical referrer<\/th>\n<th style=\"padding:10px;text-align:left;border:1px solid #ccc;\">Default GA4 bucket (pre-fix)<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"padding:10px;border:1px solid #ccc;\">ChatGPT (web)<\/td>\n<td style=\"padding:10px;border:1px solid #ccc;\">chatgpt.com<\/td>\n<td style=\"padding:10px;border:1px solid #ccc;\">Referral<\/td>\n<\/tr>\n<tr>\n<td style=\"padding:10px;border:1px solid #ccc;\">ChatGPT (desktop app)<\/td>\n<td style=\"padding:10px;border:1px solid #ccc;\">(often stripped)<\/td>\n<td style=\"padding:10px;border:1px solid #ccc;\">Direct<\/td>\n<\/tr>\n<tr>\n<td style=\"padding:10px;border:1px solid #ccc;\">Perplexity<\/td>\n<td style=\"padding:10px;border:1px solid #ccc;\">perplexity.ai<\/td>\n<td style=\"padding:10px;border:1px solid #ccc;\">Referral<\/td>\n<\/tr>\n<tr>\n<td style=\"padding:10px;border:1px solid #ccc;\">Gemini<\/td>\n<td style=\"padding:10px;border:1px solid #ccc;\">gemini.google.com<\/td>\n<td style=\"padding:10px;border:1px solid #ccc;\">Referral<\/td>\n<\/tr>\n<tr>\n<td style=\"padding:10px;border:1px solid #ccc;\">Google AI Overviews<\/td>\n<td style=\"padding:10px;border:1px solid #ccc;\">google.com\/search<\/td>\n<td style=\"padding:10px;border:1px solid #ccc;\">Organic Search<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>How do you build a custom &#8220;AI Tools&#8221; channel group in GA4?<\/h2>\n<p>Build it in Admin under Data Display, where GA4 lets you define your own grouping rules.<\/p>\n<p>Open Admin, then Channel Groups, then create a new group. Add a channel named &#8220;AI Tools,&#8221; add a condition group, set the dimension to Source, choose <em>matches regex<\/em>, and paste your pattern.<\/p>\n<p>The order matters. GA4 assigns each session to the first channel it matches, top to bottom, so drag &#8220;AI Tools&#8221; above Referral. Otherwise generic referral rules grab the session first.<\/p>\n<p>One nuance trips people up: match on Source, not Medium. AI referrals carry a medium of &#8220;referral,&#8221; so a medium-based rule would scoop up unrelated sites along with the chatbots.<\/p>\n<p>Save the group, then give GA4 a day to apply it. New channel groups affect reporting going forward and can take up to 24 hours to populate fully.<\/p>\n<p>GA4 uses <a href=\"https:\/\/github.com\/google\/re2\/wiki\/Syntax\" target=\"_blank\" rel=\"noopener nofollow external noreferrer\" data-wpel-link=\"external\">RE2 regex<\/a>, so every dot must be escaped with a backslash. A pattern that catches the major engines looks like this:<\/p>\n<pre style=\"background:#f5f5f5;border:1px solid #ddd;border-radius:4px;padding:14px;overflow:auto;font-size:0.92em;\"><code>chatgpt\\.com|chat\\.openai\\.com|perplexity\\.ai|gemini\\.google\\.com|claude\\.ai|copilot\\.microsoft\\.com|you\\.com|poe\\.com|meta\\.ai<\/code><\/pre>\n<div style=\"background:#e8f5e9;border-left:4px solid #43a047;padding:16px 20px;margin:20px 0;border-radius:4px;\">\n<strong style=\"color:#1b5e20;\">Pro Tip:<\/strong> A custom channel group reshapes reporting from the day you save it forward, and it does not rewrite historical data. Set it up early. When I configured this on a test property, the older sessions stayed in their original buckets, so the AI Tools line only filled in going forward.<\/div>\n<h2>Which referral hostnames should your regex actually catch?<\/h2>\n<p>Catch every chatbot host your audience plausibly uses, not just the big three.<\/p>\n<p>The native AI Assistant channel covers recognized engines, but new tools appear faster than the default list updates. A custom regex lets you add a host the moment you spot it in your Referral rows.<\/p>\n<table style=\"width:100%;border-collapse:collapse;margin:20px 0;\">\n<thead>\n<tr style=\"background:#1a237e;color:#fff;\">\n<th style=\"padding:10px;text-align:left;border:1px solid #ccc;\">Engine<\/th>\n<th style=\"padding:10px;text-align:left;border:1px solid #ccc;\">Hostname(s) to match<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"padding:10px;border:1px solid #ccc;\">ChatGPT (<a href=\"https:\/\/openai.com\/\" target=\"_blank\" rel=\"noopener nofollow external noreferrer\" data-wpel-link=\"external\">OpenAI<\/a>)<\/td>\n<td style=\"padding:10px;border:1px solid #ccc;\">chatgpt.com, chat.openai.com<\/td>\n<\/tr>\n<tr>\n<td style=\"padding:10px;border:1px solid #ccc;\">Perplexity<\/td>\n<td style=\"padding:10px;border:1px solid #ccc;\">perplexity.ai<\/td>\n<\/tr>\n<tr>\n<td style=\"padding:10px;border:1px solid #ccc;\">Google Gemini<\/td>\n<td style=\"padding:10px;border:1px solid #ccc;\">gemini.google.com<\/td>\n<\/tr>\n<tr>\n<td style=\"padding:10px;border:1px solid #ccc;\"><a href=\"https:\/\/www.anthropic.com\/\" target=\"_blank\" rel=\"noopener nofollow external noreferrer\" data-wpel-link=\"external\">Anthropic<\/a> Claude<\/td>\n<td style=\"padding:10px;border:1px solid #ccc;\">claude.ai<\/td>\n<\/tr>\n<tr>\n<td style=\"padding:10px;border:1px solid #ccc;\">Microsoft Copilot<\/td>\n<td style=\"padding:10px;border:1px solid #ccc;\">copilot.microsoft.com<\/td>\n<\/tr>\n<tr>\n<td style=\"padding:10px;border:1px solid #ccc;\">Others<\/td>\n<td style=\"padding:10px;border:1px solid #ccc;\">you.com, poe.com, meta.ai<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<blockquote style=\"border-left:4px solid #9e9e9e;background:#fafafa;margin:20px 0;padding:14px 20px;color:#444;font-style:italic;\"><p>According to Google&#8217;s Analytics Help documentation, GA4 evaluates channel groups in priority order and assigns each session to the first matching channel, which is why placement above the Referral channel determines whether AI sessions are isolated or absorbed.<\/p><\/blockquote>\n<figure style=\"margin:24px 0;text-align:center;\"><img decoding=\"async\" src=\"https:\/\/designcopy.net\/wp-content\/uploads\/2026\/06\/ga4-track-chatgpt-perplexity-gemini-ai-traffic-internal-2-hero.jpg\" alt=\"Why was AI traffic invisible in GA4 before this update?\" style=\"max-width:100%;height:auto;border-radius:8px;\" loading=\"lazy\" title=\"\"><\/figure>\n<h2>Do you still need a custom group now that AI Assistant is native?<\/h2>\n<p>Yes, if you want control and completeness rather than whatever Google&#8217;s default list happens to recognize.<\/p>\n<p>The native AI Assistant channel is convenient and zero-effort, and for many sites it is enough. It catches the engines Google names, including ChatGPT, Gemini, and Claude, and updates on Google&#8217;s schedule.<\/p>\n<p>A custom &#8220;AI Tools&#8221; group earns its keep in three cases. You want to add a niche engine the moment it appears, you want a label and definition that will not shift under you, or you want the AI line to behave identically across every report and Explore.<\/p>\n<p>The two are not mutually exclusive. Run the native channel for a quick glance and the custom group for analysis you control. Comparing the two also surfaces hosts Google has not yet added to its default list.<\/p>\n<h2>How do you measure conversions from AI traffic, not just sessions?<\/h2>\n<p>Use an Explore report that crosses your channel group against a key event to see whether AI visitors convert.<\/p>\n<p>Open Explore, build a free-form table, add &#8220;Session default channel group&#8221; as the row dimension, and add Sessions plus your key event or conversion as values. Now you can compare AI Assistant against Organic Search and Direct side by side.<\/p>\n<p>This is where the work pays off. Session counts tell you AI is sending people; conversion counts tell you whether those people matter.<\/p>\n<p>A worked example makes it concrete. Say AI Assistant sends 400 sessions in a month with a 3% conversion rate, while Direct sends 4,000 sessions at 1%.<\/p>\n<p>AI is the smaller bucket but the higher-quality one, converting at triple the rate. That is the kind of finding that justifies more AI-focused content, and you only see it once the channel is split out.<\/p>\n<div style=\"background:#e8f5e9;border-left:4px solid #43a047;padding:16px 20px;margin:20px 0;border-radius:4px;\">\n<strong style=\"color:#1b5e20;\">Pro Tip:<\/strong> Add a comparison or segment for landing page so you can see which articles earn AI citations that convert. If a single guide drives most of your ChatGPT and Perplexity sessions, that is your template for the next ten pages.<\/div>\n<h2>How is tracking AI traffic in GA4 different from Google Search Console?<\/h2>\n<p>GA4 measures clicks that reached your site; Google Search Console measures how Google itself surfaced you.<\/p>\n<p>Search Console reports impressions and clicks for queries that triggered AI Overviews, but it folds them into your normal Performance report rather than labeling them as AI. It tells you nothing about ChatGPT, Perplexity, or Claude, because those engines are outside Google.<\/p>\n<p>So the two tools answer different questions. Search Console hints at AI Overview exposure inside Google; GA4 captures the actual chatbot referrals that land on your pages.<\/p>\n<div style=\"background:#e8f5e9;border-left:4px solid #43a047;padding:16px 20px;margin:20px 0;border-radius:4px;\">\n<strong style=\"color:#1b5e20;\">Pro Tip:<\/strong> Read them together. If Search Console shows rising impressions on a query while your GA4 Organic Search clicks stay flat, an AI Overview is likely answering that question without sending the click. That is a signal to make the page more click-worthy, not to chase a phantom AI channel.<\/div>\n<figure style=\"margin:24px 0;text-align:center;\"><img decoding=\"async\" src=\"https:\/\/designcopy.net\/wp-content\/uploads\/2026\/06\/ga4-track-chatgpt-perplexity-gemini-ai-traffic-internal-3-hero.jpg\" alt=\"How do you build a custom &quot;AI Tools&quot; channel group in GA4?\" style=\"max-width:100%;height:auto;border-radius:8px;\" loading=\"lazy\" title=\"\"><\/figure>\n<h2>How do you confirm your AI traffic numbers are accurate?<\/h2>\n<p>Confirm them by cross-checking your custom channel against the raw referral rows it is supposed to capture.<\/p>\n<p>Open Reports, then Acquisition, then Traffic acquisition, and look at Session source. Add up the chatgpt.com, perplexity.ai, and gemini.google.com rows, then compare that total to your AI Tools channel. The numbers should line up closely.<\/p>\n<p>If they do not, your regex is probably missing a host or sitting below Referral in priority order. Fix the order first, since that single setting causes most mismatches.<\/p>\n<p>One more check: annotate May 13, 2026 on any AI traffic chart. A sudden step up around that date usually reflects GA4&#8217;s reclassification, not a real surge in visits.<\/p>\n<h2>What common mistakes break AI traffic tracking in GA4?<\/h2>\n<p>The most common mistake is leaving the custom channel below Referral, so AI sessions never reach it.<\/p>\n<p>GA4 stops at the first matching channel. If Referral sits higher, it claims chatgpt.com and perplexity.ai before your AI Tools rule ever runs, and your AI line reads zero while Referral looks healthy.<\/p>\n<p>The second mistake is forgetting to escape dots in the regex. Written as plain text, a dot matches any character, so &#8220;perplexity.ai&#8221; would also match strings you never intended. RE2 needs the backslash.<\/p>\n<p>A third trap is treating Direct as if it were clean. Some stripped-referrer AI visits hide there permanently, which means your true AI total is a floor, not an exact figure.<\/p>\n<div style=\"background:#e8f5e9;border-left:4px solid #43a047;padding:16px 20px;margin:20px 0;border-radius:4px;\">\n<strong style=\"color:#1b5e20;\">Pro Tip:<\/strong> When you report AI traffic to a client or your team, label it &#8220;AI Assistant referrals (measured floor).&#8221; That framing is honest about the stripped-referrer gap and keeps anyone from reading the number as the full picture of your AI visibility.<\/div>\n<h2>What can GA4 still not tell you about AI traffic?<\/h2>\n<p>GA4 cannot show you impressions, citations, or any visit that never produced a click.<\/p>\n<p>An AI engine can quote your page to thousands of users who read the answer and never click through. That brand exposure is real, but it leaves no session for GA4 to record.<\/p>\n<p>It also cannot separate AI Overview clicks from ordinary organic clicks, and it cannot recover referrer data that an app stripped before the session began. For those gaps you need server log analysis or a dedicated AI-visibility tool alongside GA4.<\/p>\n<div style=\"background:#e3f2fd;border-left:4px solid #1976d2;padding:16px 20px;margin:20px 0;border-radius:4px;\">\n<strong style=\"color:#0d47a1;font-size:1.1em;\">Key Takeaway:<\/strong><\/p>\n<p style=\"margin:8px 0 0;\">GA4&#8217;s native AI Assistant channel, live since May 13, 2026, finally gives chatbot traffic its own line. Pair it with a custom &#8220;AI Tools&#8221; regex group ranked above Referral to catch hosts the default list misses, then measure conversions in Explore.<\/p>\n<p style=\"margin:8px 0 0;\">Just remember the limits: AI Overview clicks stay inside Organic Search, and citations that never earn a click never appear at all.<\/p>\n<\/div>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Does the native AI Assistant channel replace a custom channel group?<\/h3>\n<p>Not fully. The native channel covers engines Google recognizes, but a custom &#8220;AI Tools&#8221; group lets you add new or niche chatbot hosts immediately and define the grouping on your own terms.<\/p>\n<h3>Why does some ChatGPT traffic still show as Direct?<\/h3>\n<p>Desktop apps and some privacy settings strip the referrer header before the visit reaches your site. With no referrer, GA4 has nothing to classify, so the session falls into Direct.<\/p>\n<h3>Can I see Google AI Overviews traffic separately in GA4?<\/h3>\n<p>No. AI Overview clicks carry a google.com\/search referrer, so GA4 counts them as Organic Search. They cannot be isolated into their own channel.<\/p>\n<h3>Will a custom channel group fix my old data?<\/h3>\n<p>No. Channel groups apply from the moment you create them onward. Historical sessions keep their original classification, so set up your AI Tools group as early as possible.<\/p>\n<h3>What regex pattern should I start with?<\/h3>\n<p>Begin with chatgpt\\.com|chat\\.openai\\.com|perplexity\\.ai|gemini\\.google\\.com|claude\\.ai|copilot\\.microsoft\\.com and add hosts as you spot them in your Referral rows. Remember GA4 uses RE2, so escape every dot.<\/p>\n<h3>Should I track AI traffic with a GA4 segment or a channel group?<\/h3>\n<p>Use a channel group for ongoing reporting, since it labels every session automatically across all reports. Use a segment for one-off analysis, such as isolating AI visitors inside a single Explore without changing your global setup.<\/p>\n<h3>Does AI traffic from ChatGPT or Perplexity count as organic?<\/h3>\n<p>No. In GA4 these are referral sessions from the chatbot&#8217;s hostname, not organic search. Only Google AI Overview clicks fold into Organic Search, because they keep a google.com\/search referrer.<\/p>\n<h3>How does this connect to getting cited by AI in the first place?<\/h3>\n<p>Tracking is the second half of the loop. First you structure content to get quoted, then you measure the visits it earns. See our guides on <a href=\"https:\/\/designcopy.net\/en\/geo-vs-seo-ai-citations\/\" data-wpel-link=\"internal\" rel=\"follow noopener noreferrer\" class=\"wpel-icon-right\">GEO vs SEO and AI citations<i class=\"wpel-icon dashicons-before dashicons-admin-page\" aria-hidden=\"true\"><\/i><\/a> and <a href=\"https:\/\/designcopy.net\/en\/aeo-get-cited-ai-overviews\/\" data-wpel-link=\"internal\" rel=\"follow noopener noreferrer\" class=\"wpel-icon-right\">getting cited in AI Overviews<i class=\"wpel-icon dashicons-before dashicons-admin-page\" aria-hidden=\"true\"><\/i><\/a>.<\/p>\n<hr>\n<p style=\"font-size:0.9em;color:#666;\"><em>Last updated: 2026-05-31. This article references Google&#8217;s publicly documented GA4 channel grouping behavior and the AI Assistant channel released on May 13, 2026.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>You optimized a page to get cited by ChatGPT and Perplexity. The citations are showing up. So where is that traffic in your reports?<\/p>\n","protected":false},"author":1,"featured_media":265478,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","rank_math_title":"","rank_math_description":"","rank_math_focus_keyword":"","footnotes":""},"categories":[1442],"tags":[1103,4666,4664,4665],"class_list":["post-265278","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai-search-evolution","tag-chatgpt","tag-ga4","tag-gemini","tag-perplexity","et-has-post-format-content","et_post_format-et-post-format-standard"],"_links":{"self":[{"href":"https:\/\/designcopy.net\/en\/wp-json\/wp\/v2\/posts\/265278","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/designcopy.net\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/designcopy.net\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/designcopy.net\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/designcopy.net\/en\/wp-json\/wp\/v2\/comments?post=265278"}],"version-history":[{"count":1,"href":"https:\/\/designcopy.net\/en\/wp-json\/wp\/v2\/posts\/265278\/revisions"}],"predecessor-version":[{"id":265404,"href":"https:\/\/designcopy.net\/en\/wp-json\/wp\/v2\/posts\/265278\/revisions\/265404"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/designcopy.net\/en\/wp-json\/wp\/v2\/media\/265478"}],"wp:attachment":[{"href":"https:\/\/designcopy.net\/en\/wp-json\/wp\/v2\/media?parent=265278"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/designcopy.net\/en\/wp-json\/wp\/v2\/categories?post=265278"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/designcopy.net\/en\/wp-json\/wp\/v2\/tags?post=265278"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}