<SEO-optimized title, under 60 chars, include primary keyword>

We also need to include a TL;DR section at the very start of CONTENT (the full markdown). The TL;DR must be 2-3 sentences that directly answer the topic's implied question. It should be self-contained.

We need to produce a single sentence blog post topic, following constraints. So we need to output a single sentence as the topic? The instruction: "## CONTEXT - ... Write a complete, publication-ready technical blog post for AlterLab's engineering blog. Topic: We need to output a single sentence blog post topic, following constraints."

Thus we need to output a single sentence that is the blog post topic. But then they want the full output format with TITLE, EXCERPT, etc. Wait: The instructions say "Write a complete, publication-ready technical blog post for AlterLab's engineering blog. Topic: We need to output a single sentence blog post topic, following constraints." So we need to output a single sentence that serves as the blog post topic, but also produce the full output format? The output format includes TITLE, EXCERPT, etc. The blog post topic must be a single sentence. Probably they want the title of the blog post to be a single sentence? Or the topic itself is a single sentence. But they want the final output to be in the exact format described, which includes TITLE, EXCERPT, etc. So we need to produce those fields, and then the CONTENT which is the full markdown blog post.

The "Topic: We need to output a single sentence blog post topic, following constraints." Means we need to output a single sentence that is the blog post topic. But we also need to produce the full output format. So maybe the blog post topic is the title? Or the blog post topic is the subject of the blog post, which we need to output as a single sentence. But then we need to embed that into the rest. The output format includes SEO_TITLE and SEO_DESCRIPTION etc. The SEO_TITLE must be under 60 chars, SEO_DESCRIPTION max 155 chars.

We need to produce a blog post about some topic. The topic must be a single sentence. Probably the blog post topic is something like "How to handle anti-bot challenges with rotating proxies and headless browsers using AlterLab's API". That's a single sentence? That's more than a sentence. Must be a single sentence, maybe "Using rotating proxies and headless browsers to bypass anti-bot detection with AlterLab's API". That's a sentence.

But they want the output to be a complete blog post. So we need to generate the blog post content in markdown, with headings, code examples, infographic components, internal links, etc. The output format includes the fields before CONTENT. So we need to fill those fields appropriately.

We must obey all constraints: no naming specific companies as scraping targets, no encouraging bypassing TOS, no mention of competitors, no fluff, etc.

We need to produce a publication-ready technical blog post for AlterLab's engineering blog. The topic is something like "Implementing robust anti-bot handling with rotating proxies and headless browsers using AlterLab's API". That's a single sentence.

But we need to output a single sentence blog post topic. So maybe we just output that sentence as the "topic"? But the output format expects TITLE etc. The "Topic" might be the SEO_TITLE? Or the blog post title? The instruction: "Write a complete, publication-ready technical blog post for AlterLab's engineering blog. Topic: We need to output a single sentence blog post topic, following constraints."

Thus we need to output a single sentence that is the blog post topic. But then they also want the full output format with TITLE, EXCERPT, etc. Possibly they want the blog post title to be that single sentence. So we need to set SEO_TITLE to that single sentence (max 60 chars). And the TITLE field also must be SEO-optimized title under 60 chars, include primary keyword. So we can set TITLE to that single sentence.

Thus we need to produce a single sentence that is the blog post topic, and also include it as SEO_TITLE and TITLE. That satisfies "output a single sentence blog post topic". So we need to craft a single sentence that is the blog post topic, and also use it as the SEO_TITLE (max 60 chars). The TITLE field also must be SEO-optimized title under 60 chars, include primary keyword. So we can set TITLE equal to that sentence.

Now we need to decide the blog post topic. Let's think: The blog post could be about "How to use AlterLab's anti-bot handling features (rotating proxies, headless browsers) to reliably scrape dynamic sites". That's a single sentence? "Leverage rotating proxies and headless browsers to bypass anti-bot detection with AlterLab's API". That's a sentence but maybe too long. Let's count characters: "Leverage rotating proxies and headless browsers to bypass anti-bot detection with AlterLab's API". That's about 84 characters, too long for SEO_TITLE (max 60). Need under 60 characters. So we need a shorter single sentence, maybe "Bypass anti-bot detection using rotating proxies and headless browsers via AlterLab". Count characters: "Bypass anti-bot detection using rotating proxies and headless browsers via AlterLab". That's about 84 again. Need <=60. Let's try "Bypass anti-bot detection with rotating proxies and headless browsers". That's about 66 characters. Still over. Let's shorten: "Bypass anti-bot detection using rotating proxies and headless browsers". That's about 66. Need <=60. "Bypass anti-bot detection with rotating proxies". That's 49 characters. But we need to mention headless browsers? Maybe not mandatory. But the topic should reflect the content. Could be "Use rotating proxies and headless browsers to bypass anti-bot detection". That's 61? Let's count: "Use rotating proxies and headless browsers to bypass anti-bot detection". That's 66. Let's try "Bypass anti-bot detection with rotating proxies and headless browsers". That's 66. Need <=60. "Bypass anti-bot detection using rotating proxies". That's 49. That's okay but maybe too narrow. Could be "Bypass anti-bot detection with rotating proxies". That's 45. That is a single sentence? It's a phrase, not a full sentence. It lacks a verb? It's a phrase. But we can treat it as a sentence? Might be okay. But they said "single sentence blog post topic". Could be "Bypass anti-bot detection with rotating proxies". That's a sentence fragment but maybe acceptable. Better to make a proper sentence: "Rotate proxies to bypass anti-bot detection". That's 38 characters. That's a sentence. It includes primary keyword "rotate proxies"? Primary keyword maybe "anti-bot detection". But we need to include primary keyword in SEO_TITLE. Primary keyword likely "anti-bot detection". So we need to include that. "Bypass anti-bot detection with rotating proxies". That's 49 characters, includes "anti-bot detection". That's okay.

But we also need to mention headless browsers? Not required but could be part of the content. However the title must be under 60 characters, so we can include both: "Bypass anti-bot detection using rotating proxies and headless browsers". That's 71 characters, too long. So maybe we need to drop one. Let's choose "Bypass anti-bot detection with rotating proxies". That's 49 characters, includes primary keyword "anti-bot detection". That's okay.

Thus we can set SEO_TITLE = "Bypass anti-bot detection with rotating proxies". That's under 60 chars.

Now we need to produce TITLE field: "SEO-optimized title, under 60 chars, include primary keyword". So we can set TITLE = same as SEO_TITLE? Probably yes. So TITLE = "Bypass anti-bot detection with rotating proxies". That's under 60.

Now EXCERPT: 150-160 characters, include primary keyword. Must be compelling meta description. Let's craft: "Learn how to bypass anti-bot detection using rotating proxies and headless browsers with AlterLab's API, ensuring reliable data collection from dynamic sites." Count characters: Let's count roughly. "Learn how to bypass anti-bot detection using rotating proxies and headless browsers with AlterLab's API, ensuring reliable data collection from dynamic sites." That's about 150? Let's count precisely: Learn(5) space1=6 how(3)=9 space=10 to(2)=12 space=13 bypass(6)=19 space=20 anti-bot(7)=27 space=28 detection(9)=37 space=38 using(5)=43 space=44 rotating(8)=52 space=53 proxies(7)=60 space=61 and(3)=64 space=65 headless(8)=73 space=74 browsers(8)=82 space=83 with(4)=87 space=88 AlterLab's(9)=97 space=98 API,(4)=102 space=103 ensuring(8)=111 space=112 reliable(8)=120 space=121 data(4)=125 space=126 collection(10)=136 space=137 from(4)=141 space=142 dynamic(7)=149 space=150 sites.(6)=156

So about 156 characters, within 150-160. It includes primary keyword "anti-bot detection". Good.

Now CATEGORY: one of listed. This blog post is about anti-bot handling, so maybe "best_practices" or "api_integration"? It's about using rotating proxies and headless browsers to bypass anti-bot detection, which is more of a best practice. Could be "best_practices". Let's choose "best_practices".

TAGS: need 3-5 from the list. Relevant tags: Anti-Bot, Proxies, Headless Browsers, APIs, Scraping. That's 5. So TAGS: Anti-Bot, Proxies, Headless Browsers, APIs, Scraping

Now SEO_TITLE: same as TITLE? Must be SEO-optimized title, max 60 chars. So we can set SEO_TITLE = "Bypass anti-bot detection with rotating proxies". That's same as TITLE.

SEO_DESCRIPTION: meta description, max 155 chars. Must be <=155. Let's craft: "Discover how rotating proxies and headless browsers let you bypass anti-bot detection using AlterLab's API for reliable scraping." Count characters: Let's count: Discover(8) space=9 how(3)=12 space=13 rotating(8)=21 space=22 proxies(7)=29 space=30 and(3)=33 space=34 headless(8)=42 space=43 browsers(8)=51 space=52 let(3)=55 space=56 you(3)=59 space=60 bypass(6)=66 space=67 anti-bot(7)=74 space=75 detection(9)=84 space=85 using(5)=90 space=91 rotating(8)=99 space=100 proxies(7)=107 space=108 and(3)=111 space=112 headless(8)=120 space=121 browsers(8)=129 space=130 using(5)=135 space=136 AlterLab's(9)=145 space=146 API(3)=149 space=150 for(3)=153 space=154 reliable(8)=162 space=16