{"id":3062,"date":"2026-10-21T12:30:00","date_gmt":"2026-10-21T09:30:00","guid":{"rendered":"https:\/\/narhost.com\/blog\/?p=3062"},"modified":"2026-10-15T11:18:10","modified_gmt":"2026-10-15T08:18:10","slug":"gmail-toplu-gonderici-kurallari","status":"publish","type":"post","link":"https:\/\/narhost.com\/blog\/gmail-toplu-gonderici-kurallari\/","title":{"rendered":"Gmail ve Yahoo Toplu G\u00f6nderici Kurallar\u0131 \u015eirket E-postan\u0131z\u0131 Nas\u0131l Etkiler"},"content":{"rendered":"<div id=\"ai-ozet\" class=\"ai-box\">\n<p class=\"ai-box-title\">K\u0131saca \u00f6zet<\/p>\n<ul>\n<li>Gmail toplu g\u00f6nderici kurallar\u0131, 1 \u015eubat 2024&#8217;ten beri Gmail&#8217;e g\u00fcnde 5.000&#8217;den fazla ileti g\u00f6nderenlerden SPF, DKIM ve DMARC&#8217;\u0131n \u00fc\u00e7\u00fcn\u00fc birden, tek t\u0131kla abonelikten \u00e7\u0131kmay\u0131 ve y\u00fczde 0,3&#8217;\u00fcn alt\u0131nda spam oran\u0131n\u0131 istiyor.<\/li>\n<li>G\u00fcnde birka\u00e7 y\u00fcz ileti g\u00f6nderen k\u00fc\u00e7\u00fck \u015firket toplu g\u00f6nderici say\u0131lmaz, ama SPF ya da DKIM, ge\u00e7erli ters DNS ve TLS \u015fart\u0131 onun i\u00e7in de ge\u00e7erlidir.<\/li>\n<li>Kimli\u011fi do\u011frulanmayan ileti Gmail&#8217;de spama d\u00fc\u015fer ya da 550 5.7.26 hatas\u0131yla geri d\u00f6ner.<\/li>\n<li>Yahoo ayn\u0131 d\u00f6nemde neredeyse ayn\u0131 kurallar\u0131 getirdi; toplu g\u00f6ndericilerden abonelikten \u00e7\u0131kma talebini 2 g\u00fcn i\u00e7inde i\u015flemesini istiyor.<\/li>\n<li>Kurumsal e-posta ile b\u00fclten ayn\u0131 alan ad\u0131ndan ve ayn\u0131 sunucudan \u00e7\u0131karsa b\u00fcltenin \u015fik\u00e2yetleri g\u00fcnl\u00fck yaz\u0131\u015fmalar\u0131n teslimini de etkiler.<\/li>\n<li>Payla\u015f\u0131ml\u0131 hostingte saatlik g\u00f6nderim s\u0131n\u0131r\u0131 vard\u0131r; binlerce ki\u015filik b\u00fclten i\u00e7in ayr\u0131 bir toplu e-posta servisi kullanmak do\u011fru yoldur.<\/li>\n<\/ul>\n<\/div>\n<p>M\u00fc\u015fteriye g\u00f6nderdi\u011finiz teklif e-postas\u0131 birden spam klas\u00f6r\u00fcne d\u00fc\u015fmeye ba\u015flad\u0131 ya da baz\u0131 Gmail adresleri iletiyi &#8220;kimlik do\u011frulanamad\u0131&#8221; diyerek geri \u00e7evirdi. Ortada bir de\u011fi\u015fiklik yapmad\u0131n\u0131z; de\u011fi\u015fen, b\u00fcy\u00fck e-posta servislerinin gelen kutusuna kimi kabul etti\u011fidir. Bu yaz\u0131 Gmail toplu g\u00f6nderici kurallar\u0131n\u0131n ne istedi\u011fini ve g\u00fcnde yaln\u0131z birka\u00e7 y\u00fcz e-posta g\u00f6nderen bir \u015firketi nas\u0131l etkiledi\u011fini anlat\u0131yor.<\/p>\n<h2>Gmail Toplu G\u00f6nderici Kurallar\u0131 Ne \u0130stiyor<\/h2>\n<p>Google, <a href=\"https:\/\/support.google.com\/mail\/answer\/81126\" title=\"Google \u2014 Gmail&#039;e e-posta g\u00f6nderenler i\u00e7in y\u00f6nergeler\" target=\"_blank\" rel=\"noopener\">g\u00f6nderici y\u00f6nergelerini<\/a> iki katmana ay\u0131r\u0131yor. Birinci katman Gmail&#8217;e ileti g\u00f6nderen herkesi kapsar; ikinci katman yaln\u0131z g\u00fcnde 5.000&#8217;den fazla ileti g\u00f6nderenler i\u00e7indir. Kurallar\u0131n b\u00fcy\u00fck b\u00f6l\u00fcm\u00fc 1 \u015eubat 2024&#8217;ten beri uygulan\u0131yor.<\/p>\n<table>\n<thead>\n<tr>\n<th>\u015eart<\/th>\n<th>B\u00fct\u00fcn g\u00f6ndericiler<\/th>\n<th>Toplu g\u00f6ndericiler (g\u00fcnde 5.000+)<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Kimlik do\u011frulama<\/td>\n<td>SPF ya da DKIM<\/td>\n<td>SPF ve DKIM birlikte<\/td>\n<\/tr>\n<tr>\n<td>DMARC<\/td>\n<td>\u00d6nerilir<\/td>\n<td>Zorunlu; en az p=none, From alan ad\u0131 hizal\u0131<\/td>\n<\/tr>\n<tr>\n<td>Ters DNS ve TLS<\/td>\n<td>Ge\u00e7erli PTR kayd\u0131, TLS ba\u011flant\u0131s\u0131<\/td>\n<td>Ayn\u0131<\/td>\n<\/tr>\n<tr>\n<td>Spam oran\u0131<\/td>\n<td>Y\u00fczde 0,3&#8217;\u00fcn alt\u0131nda<\/td>\n<td>Y\u00fczde 0,3&#8217;\u00fcn alt\u0131nda, hedef 0,1<\/td>\n<\/tr>\n<tr>\n<td>Abonelikten \u00e7\u0131kma<\/td>\n<td>Gerekmez<\/td>\n<td>Pazarlama iletisinde tek t\u0131kla \u00e7\u0131kma ve g\u00f6r\u00fcn\u00fcr ba\u011flant\u0131<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>DKIM anahtar\u0131n\u0131n en az 1024 bit olmas\u0131, 2048 bitin tercih edilmesi isteniyor. \u0130letilerin e-posta bi\u00e7im standard\u0131na (RFC 5322) uymas\u0131 ve ba\u015fkas\u0131n\u0131n Gmail adresini g\u00f6nderici olarak taklit etmemesi de b\u00fct\u00fcn g\u00f6ndericiler i\u00e7in ge\u00e7erli \u015fartlar aras\u0131nda.<\/p>\n<div class=\"highlight-box\">\n<p class=\"label\">Bilgi<\/p>\n<p>Yahoo da ayn\u0131 d\u00f6nemde neredeyse ayn\u0131 kurallar\u0131 duyurdu. <a href=\"https:\/\/senders.yahooinc.com\/best-practices\/\" title=\"Yahoo Sender Hub \u2014 g\u00f6nderici \u015fartlar\u0131 ve en iyi uygulamalar\" target=\"_blank\" rel=\"noopener\">Yahoo&#8217;nun g\u00f6nderici sayfas\u0131<\/a> toplu g\u00f6ndericilerden SPF ve DKIM&#8217;in ikisini, ge\u00e7en bir DMARC kayd\u0131n\u0131 ve abonelikten \u00e7\u0131kma taleplerinin 2 g\u00fcn i\u00e7inde i\u015flenmesini istiyor.<\/p>\n<\/div>\n<h2>Kimler Toplu G\u00f6nderici Say\u0131l\u0131r<\/h2>\n<p>Google&#8217;\u0131n e\u015fi\u011fi ki\u015fisel Gmail hesaplar\u0131na, yani @gmail.com ve @googlemail.com adreslerine g\u00fcnde 5.000&#8217;den fazla ileti g\u00f6ndermektir. Say\u0131m ki\u015fi say\u0131s\u0131yla de\u011fil ileti say\u0131s\u0131yla yap\u0131l\u0131r: \u00e7o\u011fu Gmail adresi olan 3.000 ki\u015filik bir listeye ayn\u0131 g\u00fcn iki b\u00fclten g\u00f6ndermek 6.000 ileti eder ve e\u015fi\u011fi a\u015far. Yahoo sabit bir say\u0131 vermiyor; g\u00f6ndericiyi alan ad\u0131 d\u00fczeyinde ve iletinin niteli\u011fine g\u00f6re de\u011ferlendiriyor.<\/p>\n<p>Ofis yaz\u0131\u015fmalar\u0131, teklifler, faturalar ve sipari\u015f bildirimleri g\u00f6nderen tipik bir k\u00fc\u00e7\u00fck \u015firket bu e\u015fi\u011fe yakla\u015fmaz. E\u015fi\u011fi a\u015fanlar genellikle e-b\u00fclten, kampanya duyurusu ya da e-ticaret bildirimleri g\u00f6nderen i\u015fletmelerdir.<\/p>\n<figure class=\"nh-sema\"><img loading=\"lazy\" src=\"https:\/\/narhost.com\/blog\/wp-content\/uploads\/2026\/10\/gmail-toplu-gonderici-kurallari-sema-narhost.webp\" alt=\"gmail toplu g\u00f6nderici kurallar\u0131 \u015femas\u0131 \u2014 b\u00fct\u00fcn g\u00f6ndericiler, toplu g\u00f6ndericiler ve kurulum s\u0131ras\u0131\" width=\"1200\" height=\"500\" loading=\"lazy\" decoding=\"async\"><figcaption>Kimlik do\u011frulama herkes i\u00e7in \u015fart; DMARC ve tek t\u0131kla \u00e7\u0131kma toplu g\u00f6ndericiler i\u00e7in zorunlu.<\/figcaption><\/figure>\n<h2>K\u00fc\u00e7\u00fck \u015eirket \u0130\u00e7in Ne De\u011fi\u015fti<\/h2>\n<p>Toplu g\u00f6nderici olmasan\u0131z da birinci katman\u0131n \u015fartlar\u0131 sizi ba\u011flar. Alan ad\u0131n\u0131zda SPF ve DKIM kayd\u0131 yoksa ya da yanl\u0131\u015fsa Gmail iletinizi do\u011frulayamaz. Sonu\u00e7 ya spam klas\u00f6r\u00fcd\u00fcr ya da reddedilen ileti; ret durumunda g\u00f6nderene d\u00f6nen bildirimde 5.7.26 kodu g\u00f6r\u00fcn\u00fcr. Bu hatan\u0131n ad\u0131m ad\u0131m \u00e7\u00f6z\u00fcm\u00fc <a href=\"https:\/\/narhost.com\/destek\/550-5-7-26-hatasi\/\" title=\"550 5.7.26 Kimlik Do\u011frulama Hatas\u0131 Nas\u0131l \u00c7\u00f6z\u00fcl\u00fcr \u2014 Narhost Destek Merkezi\">550 5.7.26 hatas\u0131<\/a> kart\u0131nda.<\/p>\n<p>S\u0131k g\u00f6r\u00fclen bir tuzak, alan ad\u0131ndan birden fazla yerin ileti g\u00f6ndermesidir. \u015eirket e-postas\u0131 hosting sunucusundan \u00e7\u0131kar, web sitesinin ileti\u015fim formu ba\u015fka bir servisten, muhasebe program\u0131 ise kendi sunucusundan g\u00f6nderir. SPF kayd\u0131 bunlardan yaln\u0131z birini i\u00e7eriyorsa di\u011ferlerinin iletileri do\u011frulanamaz. Kay\u0131tlar\u0131n mant\u0131\u011f\u0131 <a href=\"https:\/\/narhost.com\/blog\/e-postalar-neden-spama-duser\/\" title=\"E-postalar\u0131n\u0131z Neden Spam&#039;e D\u00fc\u015fer \u2014 Narhost Blog\">e-postalar neden spama d\u00fc\u015fer<\/a> yaz\u0131s\u0131nda anlat\u0131ld\u0131.<\/p>\n<div class=\"senaryo-block\">\n<p class=\"label\">\u00d6rnek senaryo<\/p>\n<p>Ankara&#8217;da 14 ki\u015filik bir muhasebe b\u00fcrosu m\u00fc\u015fterilerine her ay beyanname hat\u0131rlatmas\u0131 g\u00f6nderiyor; toplam 900 ileti, \u00e7o\u011fu Gmail adreslerine. Mart ay\u0131nda iletilerin bir k\u0131sm\u0131 geri d\u00f6nd\u00fc. \u0130nceleme, alan ad\u0131nda SPF kayd\u0131 oldu\u011funu ama DKIM&#8217;in hi\u00e7 kurulmad\u0131\u011f\u0131n\u0131, hat\u0131rlatmalar\u0131 g\u00f6nderen program\u0131n da SPF&#8217;de yer almad\u0131\u011f\u0131n\u0131 g\u00f6sterdi. B\u00fcro DKIM&#8217;i a\u00e7t\u0131, program\u0131n g\u00f6nderim servisini SPF&#8217;ye ekledi ve izleme politikas\u0131yla bir DMARC kayd\u0131 yay\u0131mlad\u0131. Sonraki ay Gmail&#8217;in ileti kayna\u011f\u0131nda \u00fc\u00e7 kontrol de ge\u00e7ti, geri d\u00f6n\u00fc\u015f olmad\u0131.<\/p>\n<\/div>\n<h2>Kurulum S\u0131ras\u0131 ve Kontrol<\/h2>\n<p>Do\u011fru s\u0131ra \u015fudur: \u00f6nce SPF, sonra DKIM, en son DMARC. cPanel kullanan hostinglerde ilk ikisi Email Deliverability ekran\u0131ndan tek d\u00fc\u011fmeyle kurulur; DMARC kayd\u0131 elle eklenir. DMARC&#8217;ta <code>p=none<\/code> ile ba\u015flay\u0131n, gelen raporlarla b\u00fct\u00fcn g\u00f6nderen kaynaklar\u0131n do\u011fruland\u0131\u011f\u0131n\u0131 g\u00f6rd\u00fckten sonra <code>quarantine<\/code> ya da <code>reject<\/code>&#8216;e ge\u00e7in. Politika se\u00e7imi <a href=\"https:\/\/narhost.com\/blog\/dmarc-politikasi\/\" title=\"DMARC Politikas\u0131 p=none mu quarantine mi reject mi \u2014 Narhost Blog\">DMARC politikas\u0131<\/a> yaz\u0131s\u0131nda ayr\u0131nt\u0131l\u0131 anlat\u0131ld\u0131.<\/p>\n<p>Kontrol i\u00e7in kendi alan ad\u0131n\u0131zdan bir Gmail adresine ileti g\u00f6nderin ve iletiyi a\u00e7\u0131p <strong>Orijinali g\u00f6ster<\/strong>&#8216;i se\u00e7in. SPF, DKIM ve DMARC sat\u0131rlar\u0131n\u0131n \u00fc\u00e7\u00fc <code>PASS<\/code> g\u00f6steriyorsa kurallara uyuyorsunuz. Toplu g\u00f6nderiyorsan\u0131z spam oran\u0131n\u0131 <a href=\"https:\/\/postmaster.google.com\/\" title=\"Google Postmaster Tools\" target=\"_blank\" rel=\"noopener\">Google Postmaster Tools<\/a> ile izleyin.<\/p>\n<div class=\"warn-box\">\n<p class=\"label\">Dikkat<\/p>\n<p>B\u00fclteni g\u00fcnl\u00fck yaz\u0131\u015fmalarla ayn\u0131 alan ad\u0131ndan ve ayn\u0131 sunucudan g\u00f6ndermeyin. B\u00fcltene gelen spam \u015fik\u00e2yetleri alan ad\u0131n\u0131n itibar\u0131n\u0131 d\u00fc\u015f\u00fcr\u00fcr ve teklif, fatura gibi \u00f6nemli iletilerin teslimini de etkiler. B\u00fclten i\u00e7in ayr\u0131 bir alt alan ad\u0131 (\u00f6r. <code>bulten.ornek.com<\/code>) ve toplu e-posta servisi kullan\u0131n.<\/p>\n<\/div>\n<h2>Hosting E-postas\u0131 Toplu G\u00f6nderim \u0130\u00e7in Uygun mu<\/h2>\n<p>Payla\u015f\u0131ml\u0131 hosting e-postas\u0131 g\u00fcnl\u00fck yaz\u0131\u015fma i\u00e7in tasarlan\u0131r. Narhost&#8217;ta web ve bayi hosting paketlerinde g\u00fcnl\u00fck g\u00f6nderim s\u0131n\u0131r\u0131 yoktur, ancak hesap ba\u015f\u0131na saatlik 100 e-posta s\u0131n\u0131r\u0131 vard\u0131r; giden e-postalar b\u00fct\u00fcn paketlerde bir \u00e7\u0131k\u0131\u015f aktarma sunucusu \u00fczerinden g\u00f6nderilir. Bu yap\u0131 ofis yaz\u0131\u015fmas\u0131n\u0131 rahat ta\u015f\u0131r, ama binlerce ki\u015filik bir b\u00fclten saatlere yay\u0131l\u0131r ve payla\u015f\u0131lan \u00e7\u0131k\u0131\u015f itibar\u0131n\u0131 riske atar. Se\u00e7enekler <a href=\"https:\/\/narhost.com\/blog\/toplu-mail-gonderme-hosting\/\" title=\"Toplu Mail G\u00f6nderme Hosting \u00dczerinden Yap\u0131l\u0131r m\u0131 \u2014 Narhost Blog\">toplu mail g\u00f6nderme hosting \u00fczerinden yap\u0131l\u0131r m\u0131<\/a> yaz\u0131s\u0131nda kar\u015f\u0131la\u015ft\u0131r\u0131ld\u0131.<\/p>\n<div class=\"success-box\">\n<p class=\"label\">Sonu\u00e7<\/p>\n<p>Gmail toplu g\u00f6nderici kurallar\u0131 yaln\u0131z b\u00fcy\u00fck g\u00f6ndericileri ilgilendirmiyor; SPF ya da DKIM, ters DNS ve TLS \u015fart\u0131 herkes i\u00e7in ge\u00e7erli. K\u00fc\u00e7\u00fck \u015firketin yapmas\u0131 gereken, alan ad\u0131ndan ileti g\u00f6nderen her kayna\u011f\u0131 SPF ve DKIM ile do\u011frulamak ve izleme modunda bir DMARC kayd\u0131 yay\u0131mlamakt\u0131r. B\u00fclten g\u00f6nderiyorsan\u0131z onu ayr\u0131 alt alan ad\u0131na ve ayr\u0131 servise ta\u015f\u0131y\u0131n.<\/p>\n<\/div>\n<h2>Kontrol Listesi<\/h2>\n<ul class=\"kontrol-listesi\">\n<li>Alan ad\u0131n\u0131zdan ileti g\u00f6nderen b\u00fct\u00fcn kaynaklar\u0131 listeleyin: e-posta sunucusu, form, muhasebe ya da e-ticaret yaz\u0131l\u0131m\u0131.<\/li>\n<li>SPF kayd\u0131n\u0131n bu kaynaklar\u0131n hepsini tek kay\u0131tta i\u00e7erdi\u011fini do\u011frulay\u0131n.<\/li>\n<li>DKIM imzas\u0131n\u0131 a\u00e7\u0131n; anahtar en az 1024 bit olsun.<\/li>\n<li>p=none ile bir DMARC kayd\u0131 yay\u0131mlay\u0131n ve rapor adresi tan\u0131mlay\u0131n.<\/li>\n<li>Gmail&#8217;de Orijinali g\u00f6ster ekran\u0131nda \u00fc\u00e7 kontrol\u00fcn de PASS oldu\u011funu g\u00f6r\u00fcn.<\/li>\n<li>B\u00fclten g\u00f6nderiyorsan\u0131z ayl\u0131k ileti say\u0131s\u0131n\u0131 Gmail adreslerine g\u00f6re hesaplay\u0131n.<\/li>\n<li>Pazarlama iletilerine tek t\u0131kla abonelikten \u00e7\u0131kma ve g\u00f6r\u00fcn\u00fcr ba\u011flant\u0131 ekleyin.<\/li>\n<\/ul>\n<div class=\"kb-faq\">\n<h2>S\u0131k\u00e7a sorulan sorular<\/h2>\n<h3>Gmail toplu g\u00f6nderici kurallar\u0131 Google Workspace adreslerini de kaps\u0131yor mu?<\/h3>\n<p>Google&#8217;\u0131n e\u015fik tan\u0131m\u0131 ki\u015fisel Gmail hesaplar\u0131na, yani @gmail.com ve @googlemail.com adreslerine giden iletilere dayan\u0131yor. Kimlik do\u011frulama gibi b\u00fct\u00fcn g\u00f6ndericilere y\u00f6nelik \u015fartlar ise Gmail altyap\u0131s\u0131na giden her ileti i\u00e7in ge\u00e7erli kabul edilmeli.<\/p>\n<h3>G\u00fcnde 100 e-posta g\u00f6nderiyorum, DMARC kurmam gerekir mi?<\/h3>\n<p>Google bu hacimde DMARC&#8217;\u0131 zorunlu tutmuyor; SPF ya da DKIM yeterli. Yine de DMARC kurmak alan ad\u0131n\u0131z\u0131n taklit edilmesini zorla\u015ft\u0131r\u0131r ve teslim oran\u0131n\u0131 art\u0131r\u0131r. \u0130zleme modunda bir kay\u0131t yay\u0131mlamak birka\u00e7 dakikal\u0131k i\u015ftir.<\/p>\n<h3>Spam oran\u0131 nas\u0131l \u00f6l\u00e7\u00fcl\u00fcr?<\/h3>\n<p>Gmail taraf\u0131nda Google Postmaster Tools, alan ad\u0131n\u0131z\u0131 do\u011frulad\u0131ktan sonra Gmail kullan\u0131c\u0131lar\u0131n\u0131n iletilerinizi ne oranda spam olarak i\u015faretledi\u011fini g\u00f6sterir. D\u00fc\u015f\u00fck hacimli g\u00f6ndericilerde ara\u00e7 yeterli veri g\u00f6stermeyebilir.<\/p>\n<h3>Kurallara uymazsam ne olur?<\/h3>\n<p>Kimli\u011fi do\u011frulanmayan iletiler spam klas\u00f6r\u00fcne d\u00fc\u015fer ya da 5.7.26 gibi kodlarla reddedilir. Toplu g\u00f6ndericilerde spam oran\u0131 y\u00fczde 0,3&#8217;\u00fc a\u015farsa teslim oran\u0131 d\u00fc\u015fer ve iletilerin daha b\u00fcy\u00fck b\u00f6l\u00fcm\u00fc gelen kutusuna ula\u015fmaz.<\/p>\n<h3>Tek t\u0131kla abonelikten \u00e7\u0131kma her iletide gerekli mi?<\/h3>\n<p>Hay\u0131r. \u015eart pazarlama ve abonelik iletileri i\u00e7indir. \u015eifre s\u0131f\u0131rlama, sipari\u015f onay\u0131 ya da fatura gibi i\u015flem iletileri bu \u015farttan muaft\u0131r, ama kimlik do\u011frulama \u015fart\u0131 onlar i\u00e7in de ge\u00e7erlidir.<\/p>\n<\/div>\n<div class=\"cta-box\">\n<p class=\"label\">Narhost&#8217;ta<\/p>\n<p>Kurumsal e-posta hesaplar\u0131n\u0131z cPanel&#8217;in Email Deliverability ekran\u0131ndan tek d\u00fc\u011fmeyle SPF ve DKIM ile do\u011frulan\u0131r; giden iletiler \u00e7\u0131k\u0131\u015f aktarma sunucusu \u00fczerinden g\u00f6nderilir.<\/p>\n<p><a class=\"cta-btn\" href=\"https:\/\/narhost.com\/kurumsal-e-posta\" title=\"Narhost Kurumsal E-posta paketleri\">Kurumsal e-posta paketlerini incele<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Gmail toplu g\u00f6nderici kurallar\u0131 1 \u015eubat 2024&#8217;ten beri g\u00fcnde 5.000&#8217;den fazla ileti g\u00f6nderenlerden SPF, DKIM ve DMARC&#8217;\u0131 birlikte istiyor. K\u00fc\u00e7\u00fck \u015firket toplu g\u00f6nderici say\u0131lmasa da SPF ya da DKIM, ters DNS ve TLS \u015fart\u0131 onun i\u00e7in de ge\u00e7erli.<\/p>\n","protected":false},"author":1,"featured_media":3063,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19],"tags":[],"class_list":["post-3062","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-e-posta"],"_links":{"self":[{"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/posts\/3062","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/comments?post=3062"}],"version-history":[{"count":1,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/posts\/3062\/revisions"}],"predecessor-version":[{"id":3064,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/posts\/3062\/revisions\/3064"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/media\/3063"}],"wp:attachment":[{"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/media?parent=3062"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/categories?post=3062"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/narhost.com\/blog\/wp-json\/wp\/v2\/tags?post=3062"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}