Blogspot Indexing: Get Posts Indexed Fast

Blogspot indexing can be quick because Blogger runs on Google infrastructure with automatic feeds, sitemaps, and crawl friendly HTML. This guide is for Blogspot and Blogger owners who want new posts discovered in hours or days rather than weeks. You will learn the exact visibility, feed, sitemap, Search Console, template, and linking steps that speed crawling, plus how to fix stubborn posts that stay unindexed. By the end you will have a repeatable Blogger workflow that keeps discovery fast as you publish.

Key takeaways

Blogspot covers feeds, sitemaps, and baseline markup automatically, so delays usually come from visibility settings, thin content, weak links, or custom domain errors.
Confirm visibility, custom domain redirects, HTTPS, feed settings, robots controls, and template meta output before assuming a deeper problem.
Strengthen internal hubs, labels, related posts, and evergreen pillars so new posts get immediate inbound signals.
IndexNow helps Bing, Yandex, Naver, and Seznam discovery, while Google still relies on Blogger feeds, sitemaps, Search Console, and crawl signals.

Why Blogspot can index quickly and where it stalls
Visibility, privacy and custom domain foundations
Feeds, sitemaps and robots controls in Blogger
Search Console verification and sitemap submission
Template SEO, meta output and mobile layout
Content depth, labels and duplicate thin posts
Internal linking, homepage layout and crawl depth
Publishing checklist that shortens time to crawl
Fixing stubborn posts that stay unindexed
Blogspot indexing maintenance routine for steady coverage
FAQ
Sources
Further reading

Blogspot indexing setup with feed and sitemap paths accelerating post discovery

Why Blogspot can index quickly and where it stalls

Blogspot can index quickly because Blogger integrates tightly with Google crawling paths. New posts appear in Atom and RSS feeds, in automatically generated sitemaps, and in homepage, label, and archive listings that crawlers poll frequently. The platform outputs simple HTML with titles, descriptions, headings, and image markup that needs little tuning to be crawlable. On active blogs with original posts and steady updates, time from publish to crawl is often hours to days, with indexation following soon after when quality signals are strong. Custom domains on Blogger retain these benefits when DNS, HTTPS, and redirects are configured correctly.

Stalls still occur in familiar places. New Blogspot subdomains on blogspot.com need time to earn crawl frequency, so the first weeks are slower regardless of settings. Visibility set to private, search visibility disabled during setup, or draft status left on posts blocks discovery entirely. Custom domain moves can split signals across blogspot.com and the custom host if redirects and canonicals are inconsistent. Thin posts under 200 words, syndicated copies without added value, label pages with one post each, and archive pages with overlapping excerpts can be crawled but left unindexed. Template customizations that inject noindex, duplicate meta tags, or heavy scripts can also slow rendering and decisions.

Triage with live checks that take under an hour. Open the blog in an incognito window and confirm posts load without login walls. Confirm Settings plus General plus Visibility allows search engines and that posts show Published rather than Draft or Scheduled. Open your feed at /feeds/posts/default and your sitemap paths to confirm new posts appear. In Search Console, inspect two or three missing URLs and record exact statuses such as Discovered currently not indexed, Crawled currently not indexed, Excluded by noindex, Duplicate without user selected canonical, or Soft 404. Note whether gaps affect new posts, old posts after a domain change, label pages, or static pages, because each maps to a different fix. Keep dated notes with publish and inspection dates.

Set engine scope correctly. IndexNow is an open protocol co-developed by Microsoft Bing and Yandex, supported by Bing, Yandex, Naver, Seznam, and other engines listed on the official site. Google does not support IndexNow, so Blogspot Google coverage still depends on Blogger feeds, sitemaps, Search Console inspection, and quality signals. For protocol background, see the IndexNow complete guide. Use Blogger native signals for Google speed and consider IndexNow automation only for participating engines where it applies.

Visibility, privacy and custom domain foundations

Access foundations decide whether Blogspot posts can be indexed at all. Blogger spreads controls across Settings for visibility, posts for status, pages for static content, and domains for custom hosts. A post can look finished in the editor yet remain invisible to crawlers if the whole blog is private, if search visibility is disabled, if the post is draft or scheduled, or if the custom domain serves duplicate hosts without consolidation. Fixing access first prevents wasted work on content and links that crawlers cannot yet reach.

Review settings in order. In Blogger Settings, open General and confirm Blog visibility allows public access and search engine crawling. Check Privacy or visibility toggles that may have been set to private during setup. In Posts, confirm missing items show Published with correct publish dates, not Draft or Scheduled. In Pages, confirm static pages you want indexed are published and linked, while utility pages such as test layouts remain unpublished or noindexed. Open the live blog and a sample post in an incognito window on both the custom domain and the original blogspot.com address to confirm anonymous access and consistent rendering.

Custom domains need explicit redirect and HTTPS checks. After connecting a custom domain, confirm DNS points correctly, HTTPS is enabled and enforced, and the blogspot.com address redirects to the custom domain or serves the correct canonical relationship without splitting indexation. Test http, https, www, non www, and trailing slash variants, recording status codes and final canonical URLs. Update internal links, navigation, Labels, and About pages to use the canonical host, and update external profiles and feeds to point to the custom domain. Mixed content from insecure images, widgets, or embeds can degrade rendering, so replace http assets with https equivalents. If both hosts remain indexed with similar content, set the custom domain as primary in Blogger settings, ensure canonical tags point to the custom host, and avoid linking to the legacy subdomain in new posts.

After access fixes, verify with inspection tools. Use URL Inspection to test live URLs and confirm indexable status, correct canonical, and recent crawl dates. Request revalidation for a small sample of priority posts rather than bulk requesting hundreds of URLs. Record visibility settings, domain decisions, and HTTPS states with dates so future template or DNS changes do not reintroduce blocks. Clean access is the precondition for all later speed work.

Feeds, sitemaps and robots controls in Blogger

Blogger feeds and sitemaps provide the fastest native discovery path for blogspot indexing, so they deserve explicit validation. Blogger maintains Atom and RSS feeds for all posts, per label feeds, per author feeds where relevant, plus sitemap style paths that list recent posts and pages for crawlers. Crawlers poll the homepage, feeds, and sitemaps frequently on active blogs, which is why consistent publishing shortens discovery. Most Blogger setups need no manual XML editing, only confirmation that feeds, sitemaps, and robots expose the intended canonical set.

Validate feeds first. Open /feeds/posts/default in a browser or feed reader and confirm new posts appear within minutes of publishing with correct titles, timestamps, links, and full or summary content per your settings. In Blogger Settings plus Site Feed, confirm feeds are enabled for public posts with an appropriate length. Full feeds help syndication and debugging, while summary feeds can reduce scraping, so choose based on your distribution goals rather than indexing myths. Check per label feeds for key topics to confirm they update correctly. If feeds show stale timestamps or wrong links after a custom domain change, fix domain settings and internal link hosts before debugging further, because feed URLs follow site configuration.

Check sitemap style paths and robots behavior next. Open your sitemap paths, commonly /sitemap.xml and paginated variants, and confirm they list canonical post URLs with HTTP 200 responses. Save a dated copy after major publishes. Click samples to confirm canonical hosts, not legacy subdomain variants or redirect chains. Open /robots.txt and read rules for broad blocks. Keep necessary blocks for search internals, preview endpoints, and admin paths, but ensure post, page, image, script, and style paths needed for rendering remain allowed. In Blogger Settings plus Crawlers and indexing, review custom robots header tags and custom robots.txt overrides carefully. A global noindex or broad disallow copied from staging can suppress the whole blog. Test changes with Search Console robots testing features and recheck the live file in an incognito window to rule out caching.

After cleanup, rely on native polling plus Search Console submissions rather than manual ping schemes. Keep feeds and sitemaps accurate, publish consistently, and strengthen hubs so crawlers that arrive via feeds find valuable neighborhoods. Track feed update times, sitemap inclusion times, and first crawl dates for samples to see whether native signals are healthy before adding external automation. To index blogger posts reliably, confirm each new URL appears in your blogspot sitemap within minutes and that the blogger post crawl in Search Console shows a fresh fetch with the canonical host.

Search Console verification and sitemap submission

Verification makes blogger google index work measurable through inspection, coverage, sitemap status, and performance data. Without verified Search Console properties for every hostname, including custom domain variants and the legacy blogspot.com host during transitions, teams rely on site colon searches that mislead. Blogger verification is simple through DNS or HTML tags, but it must cover the exact production host to avoid blind spots.

Create a Search Console domain property for the root to cover subdomains, plus URL prefix properties for https plus your canonical host, whether www or non www, and for the legacy blogspot.com URL during and after migration. Use DNS TXT verification for domain properties, which survives template changes, and HTML tag or DNS for URL prefix properties. Blogger Settings plus General plus Verification or theme HTML head supports meta tag verification, though DNS remains more durable. Verify Bing Webmaster Tools as well for independent crawl data and for IndexNow related reporting if you later automate Bing side submissions. Document verification methods, property names, and user access so team changes do not break monitoring.

Submit sitemaps and monitor coverage weekly. In Search Console Sitemaps, add your Blogger sitemap paths for the canonical property and confirm Submitted versus Indexed counts trend upward after fixes. Review Pages indexing grouped by status, starting with errors and unexpected exclusions. For each important missing post, inspect live status, Google selected canonical, last crawl date, and whether the page was crawled or only discovered. Sort into access, duplicate, soft 404, redirect, and quality groups, then map each to Blogger settings, template output, content depth, or architecture. Record publish dates, sitemap submissions, and inspection requests. Limit manual inspection to priority posts, letting feeds, sitemaps, and hubs handle routine discovery. Bulk requests for hundreds of URLs are ineffective given quotas and crawl capacity.

Use Bing data as a second signal. Check sitemap status and crawl stats to confirm fetches after publishes. Submit only canonical URLs without tracking parameters. If Bing fetches quickly while Google lags, that split is expected and confirms publishing works while Google specific quality or linking work continues. Keep a runbook with property names, sitemap URLs, verification methods, and escalation steps so coverage work survives staff changes.

Blogspot indexing verification and sitemap submission flow for faster indexing

Template SEO, meta output and mobile layout

Blogger templates shape what crawlers see beyond post copy, so template review is high leverage for blogspot posts indexed fast goals. Stock and well maintained custom templates generally output correct titles, descriptions, canonicals, open graph tags, and mobile responsive layouts. Issues arise from old templates with duplicate title tags, missing descriptions, hard coded canonicals to a prior domain, staging noindex left in production, or heavy widgets that slow rendering. A single header or layout file affects every post, so one fix can help hundreds of URLs at once.

Audit meta output per view. View source on a post, a static page, a label hub, and the homepage, confirming one title tag, one meta description, one canonical link, and sensible open graph tags. Confirm canonicals are absolute, use the correct custom domain host and HTTPS, and self reference for indexable posts or point to the intended consolidation target for duplicates. After custom domain moves, search theme HTML for hard coded blogspot.com canonicals, backlinks, and feed links that still point to the legacy host. Update them to the canonical domain. Validate that label and archive pages have distinct titles where possible rather than repeating the same title across dozens of views. Check custom robots header tags in Settings plus Crawlers and indexing to ensure posts default to index and follow unless a specific helper should noindex.

Layout and mobile experience affect crawl efficiency and quality judgments. Ensure posts use logical heading order with one H1 for the post title, H2 and H3 progression for sections, descriptive alt text, and standard anchors. Avoid burying article copy below large blogrolls, tag clouds, and ad widgets in the DOM order where possible, so crawlers encounter main content early. Keep sidebars focused, limit homepage post counts to balance freshness with load time, and paginate archives with standard links. Run PageSpeed Insights for mobile and desktop, compress images, limit font variants, defer non critical scripts, and keep cookie notices and popups from covering content. Test with URL Inspection rendered HTML to confirm headings, body copy, images, and links appear without interaction.

Record theme changes with dates and compare coverage before and after. If Crawled currently not indexed appears on posts that render correctly, shift focus to uniqueness and links rather than further template tweaks. A clean template directly improves blogger indexing speed because faster rendering plus accurate tags strengthens the whole blogger seo indexing foundation for every post. Theme fixes improve many posts at once, so careful versioning prevents regressions when experimenting with new layouts or widgets.

Content depth, labels and duplicate thin posts

Content quality decides whether Blogspot posts that are crawled quickly also stay indexed. Blogger makes publishing frictionless, which leads to short announcements, syndicated copies, daily link roundups with little commentary, and label pages that mirror the homepage. Crawlers may fetch everything yet index only a subset when detail pages add little distinct value or when many URLs share boilerplate. Honest review of depth, originality, and label hygiene moves more posts into the index than any submission trick.

Assess depth per post type. Sample recent posts, imported posts, and label hubs, comparing unique body copy excluding shared headers, footers, and widgets. Posts under 200 words with one image and no analysis are the most likely to remain unindexed in competitive topics. Options include expanding priority posts to 800 to 1500 words with steps, examples, images, FAQs, and data, merging thin updates into comprehensive evergreen guides, and archiving or noindexing outdated announcements rather than leaving them to dilute quality. For syndicated content, add original introductions, testing notes, or local context so the Blogger version is not a pure duplicate. Keep titles and headings specific to the post topic rather than repeating generic labels across dozens of URLs.

Labels need a controlled vocabulary. Blogger labels power topic hubs and per label feeds, which help discovery when curated. They hurt when every post creates a new single use label, when labels duplicate with plural variants, or when label pages with one excerpt compete with the post itself. Consolidate to a handful of meaningful labels that each have multiple strong posts, merge synonyms, and add unique introductions to important label hubs. Remove sitewide links to thin labels, and consider noindex for single post or low value helpers while keeping posts indexable. Ensure label hub URLs are stable and linked from navigation or pillar pages so crawlers understand topical clusters.

Track quality reassessment patiently. After expanding posts and cleaning labels, republish, strengthen internal links, and allow two to four weeks for recrawls. In Search Console, compare last crawl dates with update dates to confirm crawlers saw new copy. If Crawled currently not indexed persists after access, rendering, and duplication are clean, continue deepening content and links rather than publishing more thin posts. Fewer strong posts that stay indexed outperform many thin posts that never enter the index.

Internal linking, homepage layout and crawl depth

Internal links control how fast Blogger crawlers find new posts and how much weight those posts receive. A typical pattern is a homepage showing ten recent posts, no pillar pages, minimal related links, and label widgets linking to dozens of thin archives. New posts may have one link from the homepage for a week, then fall to page three of pagination with no other inbound links. Crawlers follow links, so deep or orphaned posts are discovered slowly and indexed less reliably, even with correct feeds and sitemaps.

Map clicks from home to representative posts before restructuring. List hubs such as home, About, Start Here, key label hubs, pillar guides, and popular posts, then count clicks to sample new and old posts. Identify orphans with no hub links and near orphans with only paginated links. Add crawlable HTML links in navigation, body content, and related posts sections, using standard anchors with href values. Build two to four pillar guides that curate the best posts per core topic with descriptive anchors and unique introductions, and link new posts from the relevant pillar on publish day. Add related posts within article bodies, not only in widgets, with specific anchors describing the target. Keep pagination as standard older posts and newer posts anchors so crawlers traverse archives fully.

Homepage layout deserves deliberate tuning. Showing too many full posts on the homepage slows load and duplicates content across paginated views, while showing too few buries new posts quickly. A balanced pattern is five to seven recent excerpts with jump links to full posts, plus curated blocks for pillars, popular posts, and editorial picks that keep priority URLs linked beyond their freshness window. Avoid sitewide links to search, filter, and date variants that multiply low value URLs. Use descriptive link text such as Blogger custom domain HTTPS checklist rather than click here on every card. Keep blogrolls and tag clouds focused, because dozens of low value outbound links dilute internal signal flow.

Measure through crawling and coverage. After restructuring, publish, verify feeds and sitemaps, and inspect deep posts to confirm reachability and indexable status. In Search Console Links, compare internal link counts before and after, and watch whether Discovered currently not indexed declines for newly linked posts. Keep navigation stable for several weeks so crawlers learn the structure. Strong hubs make every later signal stronger, because feed entries and pings that point to well connected posts lead crawlers into valuable neighborhoods.

blogspot indexing diagram: visibility privacy and custom, search console verification and, content depth labels and

Publishing checklist that shortens time to crawl

A repeatable Blogger publishing checklist shortens time from draft to crawl without spamming engines. The goal is to make every post accessible, distinct, well linked, and promptly signaled through feeds, sitemaps, and inspection for priorities. Consistent execution matters more than volume, because crawlers learn to revisit blogs that publish clean, linked, original posts on a steady cadence.

Use a pre publish checklist covering slug, meta, content, links, and media. Confirm the permalink is short, descriptive, and stable, avoiding date heavy or keyword stuffed variants that invite future renames. Write a distinct title under 60 characters, a 150 to 160 character search description in Blogger post settings, one H1 through the post title, logical H2 sections, descriptive alt text, and labels from your controlled set. Ensure at least 800 to 1200 words of original steps, examples, or testing notes for competitive topics, rather than a brief pointer that duplicates the source. Add three to five internal links to pillars, label hubs, and related posts with descriptive anchors, and plan hub placement so the post is linked from at least one authoritative page on day one. Compress images, set dimensions, and test embeds for mobile load.

After publishing, verify live state the same way every time. Confirm HTTP 200 on the canonical URL with indexable header tags in an incognito window. Confirm the post appears in the homepage, relevant label hub, per label feed, main feed, and sitemap paths. Check dates, author attribution, and canonical host. Share the canonical URL without tracking parameters in newsletters and social posts so early external signals consolidate. For priority posts, inspect in Search Console and request indexing once, then record the date. Avoid bulk requesting every post, since quotas and crawl capacity make that ineffective. Let feeds, sitemaps, and hubs handle routine discovery while inspection focuses on evergreen and revenue pieces.

Coordinate updates to preserve trust in freshness signals. When refreshing older posts, update body copy, images, links, and dates together, then republish so feeds and lastmod reflect real change. Avoid trivial timestamp bumps without improvements. Note substantive updates at the bottom of the post where helpful. Track publish dates, update dates, first crawl dates, and index dates for samples each month to see whether workflow shortens discovery. Small, steady gains beat occasional bulk pushes.

Fixing stubborn posts that stay unindexed

Stubborn blogspot not indexed cases need systematic diagnosis rather than repeated resubmission. If a post remains unindexed after two to three weeks with correct access and sitemap inclusion, work through statuses in order. For Excluded by noindex, check Settings plus Crawlers and indexing plus post level custom robots tags and theme header output, then republish. For Blocked by robots, narrow custom robots rules and retest the live robots file. For Duplicate without user selected canonical, compare the post with the Google selected canonical for overlap, links, and sitemap presence, then strengthen the intended winner with unique copy, images, FAQs, and hub links. For Soft 404, fix templates that render thin content with HTTP 200 for missing items and ensure deleted URLs return proper 404 or 410 or redirect to a close replacement. For Redirect error, shorten chains, fix loops between www and apex rules, and update internal links to point directly to finals.

Content and link upgrades resolve most quality holds. Expand the post with original testing, screenshots with alt text, steps, data, and FAQs that answer distinct queries. Remove or rewrite boilerplate that repeats across many posts. Add inbound links from the relevant pillar, label hub, and two to three related posts with descriptive anchors. Reduce competition from near duplicates by merging overlapping posts, consolidating labels, or noindexing thin helpers while keeping the priority post indexable. For background on honest limits of direct API shortcuts, see the Google Indexing API complete setup article, noting the API supports JobPosting and BroadcastEvent pages only and is not a general Blogger shortcut.

Avoid counterproductive retries. Resubmitting the same URL daily without changes does not overcome thin content or weak links. Fetching with tracking parameters fragments signals. Copying the post to a new URL creates duplicates that prolong consolidation. Buying bulk links or using black box indexer promises can trigger quality issues that make recovery harder. Instead, change one variable at a time, record dates, and allow recrawls to process improvements. If a post has little search demand and no unique angle, consider merging it into a stronger guide and redirecting rather than forcing indexation for every minor update.

Escalate deliberately when patterns persist sitewide. If many posts share Crawled currently not indexed after access, rendering, duplication, and links are clean, review overall quality, ad to content ratios, intrusive interstitials, and template speed on mobile. Check Security Issues and Manual Actions in Search Console, confirm HTTPS and domain stability, and review recent template or settings changes that coincide with the drop. Document fixes and coverage deltas weekly so you can distinguish slow recovery from no recovery and adjust focus accordingly.

Blogspot indexing maintenance routine for steady coverage

Steady fast blogspot index results come from routine care as posts, labels, templates, and domains evolve. Blogger makes publishing easy, which means labels proliferate, redirects accumulate, widgets get added, and old posts decay without review. A short monthly audit plus a light weekly publishing discipline keeps access clean, content distinct, and architecture coherent. Assign a single owner for sitemap and feed review, template and robots review, content quality, and Search Console monitoring so gaps do not persist between posts.

Monthly, cover structure, access, quality, and performance. Confirm feeds and sitemaps list only canonical production URLs with HTTP 200, and that renamed permalinks have one to one redirects. Review robots.txt, custom robots header tags, and page visibility after template or domain changes. Audit new posts for unique titles, search descriptions, headings, copy, and images, merging or archiving near duplicates and pruning single use labels. Check canonical host and trailing slash consistency, homepage post counts, pagination behavior, and label hub quality. Review mobile speed for post and hub templates, compress new media, and remove unused widgets and scripts. Verify custom domain redirects stay single hop and HTTPS remains enforced. Log each check with dates and follow ups.

Weekly, enforce publishing discipline. Before publishing, confirm permalink, search description, labels, links, and alt text. After publishing, verify live URL, hub and feed inclusion, sitemap presence, and inspect one representative post per batch. Limit manual inspection to priorities, letting feeds, sitemaps, and hubs handle routine discovery. Keep a shared sheet of publishes, redirects, label merges, and template changes so diagnosis is fast when coverage dips. For participating engines beyond Google, log any IndexNow automation separately with canonical URLs and response codes, remembering Google does not use IndexNow.

Plan for growth as the archive passes hundreds of posts. Decide which posts deserve ongoing indexation and which should consolidate, update, or noindex. Build evergreen pillars that curate best content, refresh older winners with new data instead of publishing near duplicates, and prune thin labels and date archives. Track time from publish to first crawl to index for samples each month to see whether maintenance shortens discovery. Stable Blogspot coverage reflects clean access, distinct content, coherent hubs, and patient monitoring repeated consistently.

FAQ

How fast can Blogspot posts index?

Active Blogspot blogs with original posts, clean access, and strong hubs often see new posts crawled within hours to days, with indexation following soon after when quality is strong. New subdomains may take one to three weeks for early posts while crawl frequency builds. Custom domain moves can add delay until redirects and canonicals settle. Track samples with publish, first crawl, and index dates to calibrate your blogspot google index progress over time.

Does Blogger generate a sitemap automatically?

Yes. Blogger maintains feeds and sitemap style paths for posts and pages that update on publish. You still need to verify contents, submit sitemaps in Search Console and Bing Webmaster Tools, and ensure only intended canonical URLs appear. Drafts, private posts, and test pages should not appear as public indexable entries. Check feeds and sitemaps after custom domain changes to confirm hosts updated correctly.

Why are my Blogspot posts discovered but not indexed?

Discovery without indexing means Google found the URL through feeds, sitemaps, or links but chose not to add it yet. Common causes include thin posts with little original value, duplicate label or archive variants consolidating elsewhere, weak internal links with no hub support, or recent publishing awaiting quality checks. Expand the post, link it from a pillar and label hub, confirm canonical sitemap inclusion, and allow recrawls.

Should I use my blogspot.com address or a custom domain?

A custom domain is usually better for branding and long term control, but it requires correct DNS, HTTPS, redirects, and canonicals to avoid splitting signals. Keep the custom domain as primary in Blogger settings, ensure canonicals and feeds use it, and avoid linking to the legacy subdomain in new posts. If you stay on blogspot.com, keep URLs stable and focus on content and hubs. Either choice indexes well when configured cleanly.

Can IndexNow speed up Blogspot indexing on Google?

No for Google. Google does not support IndexNow, so Blogspot Google speed still depends on Blogger feeds, sitemaps, internal links, inspection for priorities, and quality. IndexNow can help Bing, Yandex, Naver, and Seznam discovery through careful automation that submits only canonical URLs with throttling and logging. Measure each engine in its own tools rather than assuming cross engine benefit.

What should I fix first when many posts are unindexed?

Start with access and hosts. Confirm public visibility, published status, custom domain redirects, HTTPS, robots, and template meta output. Then check sitemap and feed inclusion for canonical URLs. Next strengthen content depth and label hygiene, add pillar and hub links, and inspect priority posts once. These blogspot tips work best when you review blogger search visibility per label hub rather than only sitewide, because thin labels often drag down averages while pillars grow. Change one layer at a time and monitor coverage over two to four weeks. Sitewide quality holds resolve through templates and hubs faster than through repeated manual requests.

How to Get Blogspot Posts Indexed Fast