Envia uma solicitação POST para o endpoint com o parâmetro de url para receber as principais tags de SEO, como títulos, cabeçalhos e palavras-chave da página da web
Seo Extrair - Recursos do endpoint
| Objeto | Descrição |
|---|---|
url |
[Obrigatório] The url of the website |
{"url":"http:\/\/www.nytimes.com","title":"The New York Times - Breaking News, US News, World News and Videos","keywords":"news, live updates, latest news, breaking news, local news, current events, top stories, livestream, live video, world news, us news","description":"Live news, investigations, opinion, photos and video by the journalists of The New York Times from more than 150 countries around the world. Subscribe for coverage of U.S. and international news, politics, business, technology, science, health, arts, sports and more.","og_description":"Live news, investigations, opinion, photos and video by the journalists of The New York Times from more than 150 countries around the world. Subscribe for coverage of U.S. and international news, politics, business, technology, science, health, arts, sports and more.","h1":["New York Times - Top Stories"],"h2":["What to Watch and Read ","More News ","\n\nThe Athletic Sports coverage ","Well ","Culture and Lifestyle ","\n\nAudio Podcasts and narrated articles ","\n\nGames Daily puzzles "],"h3":["Sections","","Top Stories","Newsletters","Podcasts","Sections","Top Stories","Newsletters","","Sections","","Top Stories","Newsletters","Podcasts","Sections","","Recommendations","Newsletters","Podcasts","Sections","","Columns","Newsletters","Podcasts","Sections","Topics","Columnists","Podcasts","Audio","Listen","Featured","Newsletters","Games","Play","","Community","Newsletters","Cooking","Recipes","Editors' Picks","Newsletters","","Wirecutter","Reviews","","The Best...","Newsletters","The Athletic","Leagues","Top Stories","Newsletters","Play","Sections","","Top Stories","Newsletters","Podcasts","Sections","Top Stories","Newsletters","","Sections","","Top Stories","Newsletters","Podcasts","Sections","","Recommendations","Newsletters","Podcasts","Sections","","Columns","Newsletters","Podcasts","Sections","Topics","Columnists","Podcasts","Audio","Listen","Featured","Newsletters","Games","Play","","Community","Newsletters","Cooking","Recipes","Editors' Picks","Newsletters","","Wirecutter","Reviews","","The Best...","Newsletters","The Athletic","Leagues","Top Stories","Newsletters","Play"],"links":["#site-content","#site-index","#after-dfp-ad-top","\/","\/","\/international\/","\/ca\/","https:\/\/www.nytimes.com\/es\/","https:\/\/cn.nytimes.com","https:\/\/www.nytimes.com\/section\/todayspaper","\/","https:\/\/www.nytimes.com\/section\/us","https:\/\/www.nytimes.com\/section\/us","https:\/\/www.nytimes.com\/section\/politics","https:\/\/www.nytimes.com\/section\/nyregion","https:\/\/www.nytimes.com\/spotlight\/california-news","https:\/\/www.nytimes.com\/section\/education","https:\/\/www.nytimes.com\/section\/health","https:\/\/www.nytimes.com\/section\/obituaries","https:\/\/www.nytimes.com\/section\/science","https:\/\/www.nytimes.com\/section\/climate","https:\/\/www.nytimes.com\/section\/weather","https:\/\/www.nytimes.com\/section\/sports","https:\/\/www.nytimes.com\/section\/business","https:\/\/www.nytimes.com\/section\/technology","https:\/\/www.nytimes.com\/section\/upshot","https:\/\/www.nytimes.com\/section\/magazine","https:\/\/www.nytimes.com\/news-event\/trump-transition","https:\/\/www.nytimes.com\/topic\/organization\/us-supreme-court","https:\/\/www.nytimes.com\/topic\/organization\/us-congress","https:\/\/www.nytimes.com\/news-event\/immigration-us","https:\/\/www.nytimes.com\/spotlight\/abortion-news","https:\/\/www.nytimes.com\/newsletters\/morning-briefing","https:\/\/www.nytimes.com\/newsletters\/upshot","https:\/\/www.nytimes.com\/newsletters","https:\/\/www.nytimes.com\/column\/the-daily","https:\/\/www.nytimes.com\/column\/election-run-up-podcast","https:\/\/www.nytimes.com\/spotlight\/podcasts","https:\/\/www.nytimes.com\/section\/world","https:\/\/www.nytimes.com\/section\/world","https:\/\/www.nytimes.com\/section\/world\/africa","https:\/\/www.nytimes.com\/section\/world\/americas","https:\/\/www.nytimes.com\/section\/world\/asia","https:\/\/www.nytimes.com\/section\/world\/australia","https:\/\/www.nytimes.com\/section\/world\/canada","https:\/\/www.nytimes.com\/section\/world\/europe","https:\/\/www.nytimes.com\/section\/world\/middleeast","https:\/\/www.nytimes.com\/section\/science","https:\/\/www.nytimes.com\/section\/climate","https:\/\/www.nytimes.com\/section\/weather","https:\/\/www.nytimes.com\/section\/health","https:\/\/www.nytimes.com\/section\/obituaries","https:\/\/www.nytimes.com\/news-event\/israel-hamas-gaza","https:\/\/www.nytimes.com\/news-event\/ukraine-russia","https:\/\/www.nytimes.com\/spotlight\/china-relations","https:\/\/www.nytimes.com\/column\/the-global-profile","https:\/\/www.nytimes.com\/es\/","https:\/\/www.nytimes.com\/newsletters\/morning-briefing-europe","https:\/\/www.nytimes.com\/newsletters\/the-interpreter","https:\/\/www.nytimes.com\/newsletters\/your-places-global-update","https:\/\/www.nytimes.com\/newsletters\/canada-letter","https:\/\/www.nytimes.com\/newsletters","https:\/\/www.nytimes.com\/section\/business","https:\/\/www.nytimes.com\/section\/business","https:\/\/www.nytimes.com\/section\/technology","https:\/\/www.nytimes.com\/section\/business\/economy","https:\/\/www.nytimes.com\/section\/business\/media","https:\/\/www.nytimes.com\/section\/markets-overview","https:\/\/www.nytimes.com\/section\/business\/dealbook","https:\/\/www.nytimes.com\/section\/technology\/personaltech","https:\/\/www.nytimes.com\/section\/business\/energy-environment","https:\/\/www.nytimes.com\/section\/your-money","https:\/\/www.nytimes.com\/news-event\/economy-business-us","https:\/\/www.nytimes.com\/section\/markets-overview","https:\/\/www.nytimes.com\/spotlight\/artificial-intelligence","https:\/\/www.nytimes.com\/newsletters\/dealbook","https:\/\/www.nytimes.com\/newsletters","https:\/\/www.nytimes.com\/column\/hard-fork","https:\/\/www.nytimes.com\/spotlight\/podcasts","https:\/\/www.nytimes.com\/section\/arts","https:\/\/www.nytimes.com\/section\/arts","https:\/\/www.nytimes.com\/section\/books","https:\/\/www.nytimes.com\/books\/best-sellers","https:\/\/www.nytimes.com\/section\/arts\/dance","https:\/\/www.nytimes.com\/section\/movies","https:\/\/www.nytimes.com\/section\/arts\/music","https:\/\/www.nytimes.com\/section\/arts\/television","https:\/\/www.nytimes.com\/section\/theater","https:\/\/www.nytimes.com\/spotlight\/pop-culture","https:\/\/www.nytimes.com\/section\/t-magazine","https:\/\/www.nytimes.com\/section\/arts\/design","https:\/\/www.nytimes.com\/interactive\/2024\/books\/best-books-21st-century.html","https:\/\/www.nytimes.com\/spotlight\/critics-picks","https:\/\/www.nytimes.com\/spotlight\/books-to-read","https:\/\/www.nytimes.com\/spotlight\/what-to-watch","https:\/\/www.nytimes.com\/column\/playlist","https:\/\/www.nytimes.com\/interactive\/2023\/10\/27\/arts\/music\/music-fivemins-collection.html","https:\/\/www.nytimes.com\/newsletters\/read-like-the-wind","https:\/\/www.nytimes.com\/newsletters\/watching","https:\/\/www.nytimes.com\/newsletters","https:\/\/www.nytimes.com\/column\/book-review-podcast","https:\/\/www.nytimes.com\/column\/popcast-pop-music-podcast","https:\/\/www.nytimes.com\/spotlight\/podcasts","https:\/\/www.nytimes.com\/spotlight\/lifestyle","https:\/\/www.nytimes.com\/spotlight\/lifestyle","https:\/\/www.nytimes.com\/section\/well","https:\/\/www.nytimes.com\/section\/travel","https:\/\/www.nytimes.com\/section\/style","https:\/\/www.nytimes.com\/section\/realestate","https:\/\/www.nytimes.com\/section\/food","https:\/\/www.nytimes.com\/section\/fashion\/weddings","https:\/\/www.nytimes.com\/section\/your-money","https:\/\/www.nytimes.com\/section\/technology\/personaltech","https:\/\/www.nytimes.com\/section\/t-magazine","https:\/\/www.nytimes.com\/column\/36-hours","https:\/\/www.nytimes.com\/column\/ask-well","https:\/\/www.nytimes.com\/column\/the-hunt","https:\/\/www.nytimes.com\/column\/modern-love","https:\/\/www.nytimes.com\/spotlight\/best-restaurants","https:\/\/www.nytimes.com\/column\/vows","https:\/\/www.nytimes.com\/column\/social-qs","https:\/\/www.nytimes.com\/column\/the-ethicist","https:\/\/www.nytimes.com\/interactive\/2024\/us\/2024-gift-guide.html","https:\/\/www.nytimes.com\/newsletters\/open-thread-fashion","https:\/\/www.nytimes.com\/newsletters\/well","https:\/\/www.nytimes.com\/newsletters","https:\/\/www.nytimes.com\/column\/modern-love-podcast","https:\/\/www.nytimes.com\/spotlight\/podcasts","https:\/\/www.nytimes.com\/section\/opinion","https:\/\/www.nytimes.com\/section\/opinion","https:\/\/www.nytimes.com\/section\/opinion\/contributors","https:\/\/www.nytimes.com\/section\/opinion\/editorials","https:\/\/www.nytimes.com\/column\/op-docs","https:\/\/www.nytimes.com\/spotlight\/opinion-video","https:\/\/www.nytimes.com\/section\/opinion\/letters","https:\/\/www.nytimes.com\/section\/opinion\/politics","https:\/\/www.nytimes.com\/section\/opinion\/international-world","https:\/\/www.nytimes.com\/section\/opinion\/business-economics","https:\/\/www.nytimes.com\/section\/opinion\/technology","https:\/\/www.nytimes.com\/section\/opinion\/environment","https:\/\/www.nytimes.com\/section\/opinion\/health","https:\/\/www.nytimes.com\/section\/opinion\/culture","https:\/\/www.nytimes.com\/by\/charles-m-blow","https:\/\/www.nytimes.com\/by\/jamelle-bouie","https:\/\/www.nytimes.com\/by\/david-brooks","https:\/\/www.nytimes.com\/by\/gail-collins","https:\/\/www.nytimes.com\/by\/ross-douthat","https:\/\/www.nytimes.com\/by\/maureen-dowd","https:\/\/www.nytimes.com\/by\/david-french","https:\/\/www.nytimes.com\/by\/thomas-l-friedman","https:\/\/www.nytimes.com\/by\/m-gessen","https:\/\/www.nytimes.com\/by\/michelle-goldberg","https:\/\/www.nytimes.com\/by\/ezra-klein","https:\/\/www.nytimes.com\/by\/nicholas-kristof","https:\/\/www.nytimes.com\/by\/paul-krugman","https:\/\/www.nytimes.com\/by\/carlos-lozada","https:\/\/www.nytimes.com\/by\/tressie-mcmillan-cottom","https:\/\/www.nytimes.com\/by\/pamela-paul"],"_note":"Response truncated for documentation purposes"}
curl --location --request POST 'https://zylalabs.com/api/5502/web+content+scanner+api/7139/seo+extract?url=https://www.nytimes.com/' --header 'Authorization: Bearer YOUR_API_KEY'
| Cabeçalho | Descrição |
|---|---|
Authorization
|
[Obrigatório] Deve ser Bearer access_key. Veja "Sua chave de acesso à API" acima quando você estiver inscrito. |
Sem compromisso de longo prazo. Faça upgrade, downgrade ou cancele a qualquer momento. O teste gratuito inclui até 50 requisições.
A API Web Content Scanner analisa uma URL para extrair tags HTML essenciais como títulos descrições palavras-chave e cabeçalhos o que ajuda a otimizar a relevância de SEO da página
A API pode extrair elementos HTML essenciais, incluindo o título, descrição, palavras-chave, cabeçalhos H1, H2, H3 e uma lista de links na página
A API pode rastrear modificações em uma página ao longo do tempo permitindo que os usuários detectem alterações em palavras-chave cabeçalhos ou links relevantes o que é útil para análises contínuas de SEO
A API do Scanner de Conteúdo da Web funciona de forma síncrona fornecendo resultados imediatos após a análise da página da web
Desenvolvedores e especialistas em SEO podem se beneficiar desta API pois ela permite que integrem a análise automatizada de páginas em suas ferramentas melhorando os esforços de otimização para motores de busca
Ambos os endpoints retornam tags chave de SEO da página da web analisada, incluindo o título, descrição, palavras-chave, cabeçalhos H1, H2, H3 e uma lista de links. Esses dados ajudam os usuários a entender a estrutura de SEO da página
Os campos-chave nos dados de resposta incluem "url", "título", "palavras-chave", "descrição", "og_description" e cabeçalhos como "h1", "h2" e "h3" Cada campo fornece informações essenciais para a análise de SEO
Os dados de resposta estão estruturados no formato JSON, com cada chave representando um elemento SEO específico. Por exemplo, "h1" é um array contendo cabeçalhos H1, enquanto "keywords" é uma string separada por vírgulas de termos relevantes
O parâmetro principal para ambos os endpoints é "url" que especifica a página da web a ser analisada Os usuários devem fornecer uma URL válida para receber os dados de SEO correspondentes
Os usuários podem personalizar suas solicitações especificando diferentes URLs para analisar No entanto a API não suporta atualmente parâmetros adicionais para filtrar ou modificar os dados retornados
Casos de uso típicos incluem auditorias de SEO, otimização de conteúdo, análise competitiva e monitoramento de alterações em páginas da web ao longo do tempo. Esses dados ajudam os usuários a melhorar a visibilidade do seu site nos motores de busca
A precisão dos dados é mantida através da análise direta de páginas da web em tempo real pela API garantindo que as tags SEO extraídas reflitam as informações mais atuais disponíveis na URL especificada
Se os usuários receberem resultados parciais ou vazios, eles devem verificar a URL quanto à correção e garantir que a página esteja acessível Além disso, eles podem verificar possíveis problemas com a estrutura HTML da página web
Nível de serviço:
100%
Tempo de resposta:
5.312ms
Nível de serviço:
100%
Tempo de resposta:
878ms
Nível de serviço:
100%
Tempo de resposta:
5.368ms
Nível de serviço:
100%
Tempo de resposta:
2.845ms
Nível de serviço:
100%
Tempo de resposta:
213ms
Nível de serviço:
100%
Tempo de resposta:
1.880ms
Nível de serviço:
100%
Tempo de resposta:
799ms
Nível de serviço:
100%
Tempo de resposta:
884ms
Nível de serviço:
100%
Tempo de resposta:
2.381ms
Nível de serviço:
100%
Tempo de resposta:
1.374ms
Nível de serviço:
100%
Tempo de resposta:
355ms
Nível de serviço:
100%
Tempo de resposta:
2.081ms
Nível de serviço:
100%
Tempo de resposta:
604ms
Nível de serviço:
100%
Tempo de resposta:
468ms
Nível de serviço:
100%
Tempo de resposta:
337ms
Nível de serviço:
100%
Tempo de resposta:
267ms
Nível de serviço:
100%
Tempo de resposta:
339ms
Nível de serviço:
100%
Tempo de resposta:
568ms
Nível de serviço:
100%
Tempo de resposta:
5.792ms
Nível de serviço:
100%
Tempo de resposta:
6.153ms