A customer has a project on Vercel and they want to redirect the /blog path to another website. Please write a reply to the customer. Separately, list any relevant documentation you found and any feedback or information you’d like to share about your decision making process.
Hi John, Thanks for getting in touch, happy to assist you here. There are a couple of considerations to begin with. i.e. do you want search engines to treat the redirect as permanent and so cache the content of your wordpress site when scraping your Vercel site? I note that you have not utilised the app router function in your design which has recently become stable in the 13.4 release, which would be perfect for this use, as I can see that the blog page is referenced in a few places on your news and holiday photos page. So, my suggestion is to create a redirect there, like so [code to put in file and file location specific to Johns site] I would suggest looking into the app router functionality, as there are some built in SEO features you may be interested in leveraging. You can implement functions incrementally and utilising it will only help to further streamline your sites design in the future. You can study it in detail here and may also be interested in other parts of the release. If you have any questions please don’t hesitate to reach out. https://nextjs.org/blog/next-13-4#nextjs-app-router Kind regards, Rob —---------- I think the function to do this most elegantly is using redirects within the app router function. looked at the above link, and here: https://nextjs.org/docs/pages/api-reference/next-config-js/redirects
A customer is creating a site and would like their project not to be indexed by search engines. Please write a reply to the customer. Separately, list any relevant documentation you found and any feedback or information you’d like to share about your decision making process.
Hi Jerry, Glad you reached out, happy to assist you with this, welcome to the Next.js ecosystem. To prevent search engine indexing you can add a meta tag to your pages as shown here:
https://nextjs.org/learn/seo/crawling-and-indexing/metatagsTo easily manage this, and adjust if later you decide to make changes, you can create a global header that will be present on all your routes. References
https://nextjs.org/docs/pages/api-reference/next-config-js/headers and https://nextjs.org/docs/pages/api-reference/components/head https://nextjs.org/learn/seo/crawling-and-indexing/metatags
What do you think is one of the most common problems which customers ask Vercel for help with? How would you help customers to overcome common problems, short-term and long-term?
I’d say usually basic setup. Coming from legacy environments with tech/code debt. How to better leverage new features or vercel infrastructure more effectively. vercel Debugging poor code or failed builds. Advice or assistance implementing new features/releases - like recent app route, or similar uplift/patching type questions and issues around that. row into a modern full stack integrated framework approach such as Next.js.
How could we improve or alter this familiarization exercise?
I found the exercise excellent, and its great having an actual build task to complete to steer research to practical considerations and to see firsthand the power of next.js and the environment. The only thing that would have made it more interesting for me would be a question with a detailed scenario from a large customer - i.e. high traffic, large content, complex implementation to firstly get an insight into such interactions and the scale that large deployments are using next.js. Looking forward to seeing and learning about such builds. Personally, if I count my research time, completing this questionnaire and tasks took quite a bit more than three hours, with time at keyboard would be around 3 hours, and the research was useful and enjoyable and opening many doors and tangents for further questions.
Back to Home page