Envía una solicitud POST al punto final con el parámetro de url para recibir las principales etiquetas SEO, como títulos, encabezados y palabras clave de la página web.
Seo Extract - Características del Endpoint
| Objeto | Descripción |
|---|---|
url |
[Requerido] 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'
| Encabezado | Descripción |
|---|---|
Autorización
|
[Requerido] Debería ser Bearer access_key. Consulta "Tu Clave de Acceso a la API" arriba cuando estés suscrito. |
Sin compromiso a largo plazo. Mejora, reduce o cancela en cualquier momento. La Prueba Gratuita incluye hasta 50 solicitudes.
La API del Escáner de Contenido Web analiza una URL para extraer etiquetas HTML clave como títulos, descripciones, palabras clave y encabezados, lo que ayuda a optimizar la relevancia SEO de la página.
La API puede extraer elementos HTML esenciales, incluyendo el título, la descripción, las palabras clave, los encabezados H1, H2, H3 y una lista de enlaces en la página.
La API puede rastrear modificaciones en una página a lo largo del tiempo, lo que permite a los usuarios detectar cambios en las palabras clave, los encabezados o los enlaces relevantes, lo cual es útil para un análisis de SEO continuo.
La API del Escáner de Contenido Web funciona de manera sincrónica, proporcionando resultados inmediatos tras el análisis de la página web.
Los desarrolladores y los especialistas en SEO pueden beneficiarse de esta API, ya que les permite integrar análisis de páginas automatizados en sus herramientas, mejorando los esfuerzos de optimización de motores de búsqueda.
Ambos endpoints devuelven las etiquetas clave de SEO de la página web analizada, incluyendo el título, la descripción, palabras clave, encabezados H1, H2, H3 y una lista de enlaces. Estos datos ayudan a los usuarios a comprender la estructura SEO de la página.
Los campos clave en los datos de respuesta incluyen "url," "título," "palabras clave," "descripción," "og_descripción," y encabezados como "h1," "h2," y "h3." Cada campo proporciona información esencial para el análisis SEO.
Los datos de respuesta están estructurados en formato JSON, donde cada clave representa un elemento SEO específico. Por ejemplo, "h1" es un arreglo que contiene encabezados H1, mientras que "keywords" es una cadena de términos relevantes separados por comas.
El parámetro principal para ambos puntos finales es "url," que especifica la página web a analizar. Los usuarios deben proporcionar una URL válida para recibir los datos de SEO correspondientes.
Los usuarios pueden personalizar sus solicitudes especificando diferentes URL para analizar. Sin embargo, la API actualmente no admite parámetros adicionales para filtrar o modificar los datos devueltos.
Los casos de uso típicos incluyen auditorías de SEO, optimización de contenido, análisis competitivo y monitoreo de cambios en páginas web a lo largo del tiempo. Estos datos ayudan a los usuarios a mejorar la visibilidad de su sitio web en los motores de búsqueda.
La precisión de los datos se mantiene a través del análisis directo de páginas web en vivo por parte de la API, asegurando que las etiquetas SEO extraídas reflejen la información más actual disponible en la URL especificada.
Si los usuarios reciben resultados parciales o vacíos, deben verificar la URL para asegurarse de que sea correcta y garantizar que la página sea accesible. Además, pueden revisar si hay problemas potenciales con la estructura HTML de la página web.
Nivel de Servicio:
100%
Tiempo de Respuesta:
878ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
256ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
5.312ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
884ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
5.368ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
2.017ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
236ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
2.845ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
1.586ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
1.374ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
6.834ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
2.964ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
9.067ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
1.376ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
123ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
2.224ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
4.589ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
6.478ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
97ms
Nivel de Servicio:
100%
Tiempo de Respuesta:
105ms