[{"_1":2,"_177":-5,"_178":-5},"loaderData",{"_3":4,"_18":19,"_26":27,"_152":153},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16,"_17":11},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","dockerRebrandTour","routes/_layout",{"_20":-5,"_21":22,"_23":22,"_24":11,"_25":22},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_28":29,"_30":-5,"_31":11,"_32":11,"_33":34,"_35":36,"_37":-5,"_38":11,"_39":40,"_89":-5,"_90":91,"_140":-5,"_141":11,"_142":22,"_143":11,"_144":11,"_145":-5,"_146":11,"_147":-5,"_148":149,"_150":92,"_151":-7},"canonicalUrl","https://hub.docker.com/r/zerosuxx/prerender/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","zerosuxx","reponame","prerender","cloudBuildSource","isAutobuildsAvailable","repo",{"_41":42,"_43":44,"_46":47,"_48":49,"_50":11,"_51":52,"_53":54,"_55":56,"_58":36,"_33":34,"_59":60,"_61":45,"_62":63,"_64":63,"_65":66,"_67":-5,"_68":69,"_70":71,"_72":11,"_73":34,"_74":75,"_80":22,"_81":82,"_86":34,"_87":88},"categories",[],"content_types",[45],"image","date_registered","2018-05-23T10:07:32.487019Z","description","Prerender Server","is_private","last_updated","2019-07-08T20:55:50.283547Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[57],"application/vnd.docker.container.image.v1+json","name","pull_count",366,"repository_type","star_count",1,"status","status_description","active","source","collaborator_count",0,"full_description","Prerender\n===========================\n\nPrerender is a node server that uses Headless Chrome to render HTML, screenshots, PDFs, and HAR files out of any web page. The Prerender server listens for an http request, takes the URL and loads it in Headless Chrome, waits for the page to finish loading by waiting for the network to be idle, and then returns your content.\n\nLooking for our PhantomJS Prerender server? [Go to our phantomjs branch](https://github.com/prerender/prerender/tree/phantomjs)\n\n##### The quickest way to run your own prerender server:\n\n```bash\n$ npm install prerender\n```\n##### server.js\n```js\nconst prerender = require('prerender');\nconst server = prerender();\nserver.start();\n```\n##### test it:\n```bash\ncurl http://localhost:3000/render?url=https://www.example.com/\n```\n\n## Use Cases\nThe Prerender server can be used in conjunction with [our Prerender.io middleware](#middleware) in order to serve the prerendered HTML of your javascript website to search engines (Google, Bing, etc) and social networks (Facebook, Twitter, etc) for SEO. We run the Prerender server at scale for SEO needs at [https://prerender.io/](https://prerender.io/).\n\nThe Prerender server can be used on its own to crawl any web page and pull down the content for your own parsing needs. We host the Prerender server for your own crawling needs at [https://prerender.com/](https://prerender.com/).\n\n\nPrerender differs from Google Puppeteer in that Prerender is a web server that takes in URLs and loads them in parallel in a new tab in Headless Chrome. Puppeteer is an API for interacting with Chrome, but you still have to write that interaction yourself. With Prerender, you don't have to write any code to launch Chrome, load pages, wait for the page to load, or pull the content off of the page. The Prerender server handles all of that for you so you can focus on more important things!\n\nBelow you will find documentation for our Prerender.io service (website SEO) and our Prerender.com service (web crawling).\n\n[Click here to jump to Prerender.io documentation](#prerenderio)\n\n[Click here to jump to Prerender.com documentation](#prerendercom)\n\n\n### \n# Prerender.io\n###### For serving your prerendered HTML to crawlers for SEO\n\nPrerender adheres to Google's `_escaped_fragment_` proposal, which we recommend you use. It's easy:\n- Just add <meta name=\"fragment\" content=\"!\"> to the <head> of all of your pages\n- If you use hash urls (#), change them to the hash-bang (#!)\n- That's it! Perfect SEO on javascript pages.\n\n\n### \n## Middleware\n\nThis is a list of middleware available to use with the prerender service:\n\n#### Official middleware\n\n###### Javascript\n* [prerender-node](https://github.com/prerender/prerender-node) (Express)\n\n###### Ruby\n* [prerender_rails](https://github.com/prerender/prerender_rails) (Rails)\n\n###### Apache\n* [.htaccess](https://gist.github.com/thoop/8072354)\n\n###### Nginx\n* [nginx.conf](https://gist.github.com/thoop/8165802)\n\n#### Community middleware\n\n###### PHP\n* [zfr-prerender](https://github.com/zf-fr/zfr-prerender) (Zend Framework 2)\n* [YuccaPrerenderBundle](https://github.com/rjanot/YuccaPrerenderBundle) (Symfony 2)\n* [Laravel Prerender](https://github.com/JeroenNoten/Laravel-Prerender) (Laravel)\n\n###### Java\n* [prerender-java](https://github.com/greengerong/prerender-java)\n\n###### Go\n* [goprerender](https://github.com/tampajohn/goprerender)\n\n###### Grails\n* [grails-prerender](https://github.com/tuler/grails-prerender)\n\n###### Nginx\n* [Reverse Proxy Example](https://gist.github.com/Stanback/6998085)\n\n###### Apache\n* [.htaccess](https://gist.github.com/Stanback/7028309)\n\nRequest more middleware for a different framework in this [issue](https://github.com/prerender/prerender/issues/12).\n\n\n\n## How it works\nThis is a simple service that only takes a url and returns the rendered HTML (with all script tags removed).\n\nNote: you should proxy the request through your server (using middleware) so that any relative links to CSS/images/etc still work.\n\n`GET https://service.prerender.io/https://www.google.com`\n\n`GET https://service.prerender.io/https://www.google.com/search?q=angular`\n\n\n## Running locally\nIf you are trying to test Prerender with your website on localhost, you'll have to run the Prerender server locally so that Prerender can access your local dev website.\n\nIf you are running the prerender service locally. Make sure you set your middleware to point to your local Prerender server with:\n\n`export PRERENDER_SERVICE_URL=http://localhost:3000`\n\n\t$ git clone https://github.com/prerender/prerender.git\n\t$ cd prerender\n\t$ npm install\n\t$ node server.js\n\nPrerender will now be running on http://localhost:3000. If you wanted to start a web app that ran on say, http://localhost:8000, you can now visit the URL http://localhost:3000/http://localhost:8000 to see how your app would render in Prerender.\n\nTo test how your website will render through Prerender using the middleware, you'll want to visit the URL http://localhost:8000?_escaped_fragment_=\n\nThat should send a request to the Prerender server and display the prerendered page through your website. If you View Source of that page, you should see the HTML with all of the `

zerosuxx/prerender

Tags for zerosuxx/prerender